Triple
T29248151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galford |
E741490
|
entity |
| Predicate | combatPartner |
P140399
|
FINISHED |
| Object | Poppy |
—
|
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: Poppy | Statement: [Galford, combatPartner, Poppy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatPartner Context triple: [Galford, combatPartner, Poppy]
-
A.
partnerInBattle
chosen
Indicates that two entities are allied or cooperate as partners in the same battle or combat engagement.
-
B.
defencePartner
Indicates a relationship where one entity collaborates with or supports another in matters of defense or security.
-
C.
partnerInMission
Indicates that two or more entities collaborate as partners in carrying out the same mission or operation.
-
D.
wasCompanionOf
Indicates that one entity accompanied or associated closely with another, typically as a partner, ally, or fellow participant over some period of time.
-
E.
strategicPartnerForces
Indicates a formal alliance in which one force provides coordinated military or security support to another as part of a shared strategic objective.
- 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f676f968d08190a4adba0439b438c9 |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 28, 2026, 12:33 p.m.