Triple
T37541197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sgt. Byrd |
E933328
|
entity |
| Predicate | appearsAsAllyIn |
P188232
|
FINISHED |
| Object | Spyro: Year of the Dragon |
—
|
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: Spyro: Year of the Dragon | Statement: [Sgt. Byrd, appearsAsAllyIn, Spyro: Year of the Dragon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsAsAllyIn Context triple: [Sgt. Byrd, appearsAsAllyIn, Spyro: Year of the Dragon]
-
A.
alliesOf
Indicates that one entity is in a cooperative, supportive, or mutually beneficial alliance with another entity.
-
B.
alliesIncluded
Indicates that the specified set or group explicitly includes one or more allied entities as members.
-
C.
isPlayableAllyOf
chosen
Indicates that one entity can be used or controlled as an ally in conjunction with another entity, typically within a game or interactive context.
-
D.
sometimesAllyOf
Indicates that one entity is an ally of another in some situations or periods, but not consistently or universally.
-
E.
partnerInBattle
Indicates that two entities are allied or cooperate as partners in the same battle or combat engagement.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fec00f27988190955de6b6348a4d97 |
completed | May 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69febd52037c8190b475dbd50fdbc13e |
completed | May 9, 2026, 4:51 a.m. |
Created at: May 3, 2026, 4:17 p.m.