Triple
T37553415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gromgol Base Camp |
E933640
|
entity |
| Predicate | hasFlightMasterFor |
P101125
|
FINISHED |
| Object | Horde |
—
|
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: Horde | Statement: [Gromgol Base Camp, hasFlightMasterFor, Horde]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFlightMasterFor Context triple: [Gromgol Base Camp, hasFlightMasterFor, Horde]
-
A.
hasFlightMaster
chosen
Indicates that an entity provides or is associated with a flight master service or function for another entity.
-
B.
hasSwordmaster
Indicates that an entity is associated with or possesses a designated swordmaster, typically as a mentor, trainer, or specialist in swordsmanship.
-
C.
isMasterOf
Indicates that one entity holds a position of control, authority, or ownership over another entity.
-
D.
hasTalons
Indicates that an entity possesses talons as a physical feature.
-
E.
hasLockFlight
Indicates that one entity is associated with a specific lock flight, representing a relationship where the entity uses, contains, or is located at that sequence of canal locks.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:17 p.m.