Triple
T25149199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magical Elves |
E630021
|
entity |
| Predicate | originalNetworkPartners |
P142469
|
FINISHED |
| Object | Bravo |
—
|
NE NERFINISHED |
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: Bravo | Statement: [Magical Elves, originalNetworkPartners, Bravo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalNetworkPartners Context triple: [Magical Elves, originalNetworkPartners, Bravo]
-
A.
originalNetworkPartner
chosen
Indicates that one entity is the initial or primary collaborating partner of another within a network or partnership context.
-
B.
primaryPartners
Indicates that the entities are each other’s main or most significant partners in a relationship, typically implying priority or exclusivity over other partnerships.
-
C.
hasNetworkPartner
Indicates that an entity is connected to another entity through a formal or recognized network partnership relationship.
-
D.
announcesNetworkPartner
Indicates that one entity publicly declares or makes known another entity as its partner within a network or collaborative framework.
-
E.
exportPartners
Indicates a relationship where one entity collaborates with or serves as a partner to another in exporting goods or services across borders.
- F. None of above.
Provenance (3 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_69e2ff349e408190a6f4a5a66279f54d |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 18, 2026, 6:30 a.m.