Triple
T30894138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AAR Consortium |
E786977
|
entity |
| Predicate | roleInTNK-BP |
P200452
|
FINISHED |
| Object | joint venture shareholder |
—
|
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: joint venture shareholder | Statement: [AAR Consortium, roleInTNK-BP, joint venture shareholder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInTNK-BP Context triple: [AAR Consortium, roleInTNK-BP, joint venture shareholder]
-
A.
roleInBladeTrinity
Indicates that an entity participated in the movie "Blade: Trinity" in a specific role (such as actor, director, or crew position).
-
B.
BIJACRole
Indicates a role-based relationship where an entity participates in or is assigned a specific role within a BIJAC context or structure.
-
C.
RykTulbaghRole
Indicates that an entity holds or is associated with a specific role or position in relation to Ryk Tulbagh.
-
D.
roleInBun
Indicates that an entity has a specific functional or contextual role within a particular bundle, grouping, or composite structure.
-
E.
roleInBladeII
Indicates that an entity has a specific role or participation in the movie "Blade II."
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff8ba3f8248190bbdf8e7ec2b35093 |
completed | May 9, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69ff8b41ba988190a7332e8317d10f09 |
completed | May 9, 2026, 7:30 p.m. |
| PDg | Predicate description generation | batch_69ff8ba329e08190813e728f0d1bd973 |
completed | May 9, 2026, 7:31 p.m. |
Created at: April 29, 2026, 8:49 p.m.