Triple
T36068493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nyoin |
E1043298
|
entity |
| Predicate | statusComparedToOtherConsorts |
P200583
|
FINISHED |
| Object | higher |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: higher | Statement: [Nyoin, statusComparedToOtherConsorts, higher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusComparedToOtherConsorts Context triple: [Nyoin, statusComparedToOtherConsorts, higher]
-
A.
associatedConsort
Indicates a spousal or consort relationship linking one entity to another as their partner.
-
B.
linkedToConsort
Indicates a relationship in which one entity is connected or associated to another as its consort (spouse or formal partner).
-
C.
holderConsort
Indicates a marital or consort relationship in which one entity is the spouse or consort of the title- or office-holding entity.
-
D.
hasNumberOfMemberInstitutions
Indicates the quantitative count of member institutions associated with a given entity.
-
E.
usesConsortiumModel
Indicates that an entity operates under or applies a consortium-based model, typically involving shared governance, resources, or collaboration among multiple organizations.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff97637ad881908c24fe2cc6b036db |
completed | May 9, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69ff96c43a808190942eeda1934602db |
completed | May 9, 2026, 8:19 p.m. |
| PDg | Predicate description generation | batch_69ff976281888190a2e872296fb4a661 |
completed | May 9, 2026, 8:21 p.m. |
Created at: May 3, 2026, 4:08 p.m.