Triple
T37961110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wandering Trader |
E947009
|
entity |
| Predicate | fleeFrom |
P11257
|
FINISHED |
| Object | hostile mobs |
—
|
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: hostile mobs | Statement: [Wandering Trader, fleeFrom, hostile mobs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fleeFrom Context triple: [Wandering Trader, fleeFrom, hostile mobs]
-
A.
fledFrom
chosen
Indicates that one entity escaped or ran away from another entity or location.
-
B.
fleesTo
Indicates that an entity escapes or runs away from a place, situation, or threat and goes to a specific destination.
-
C.
fleesWith
Indicates that one entity escapes or runs away together with another entity, sharing the act of fleeing as companions or partners.
-
D.
someFledTo
Indicates that at least one member of a group escaped or ran away from one place and went to another place.
-
E.
plansToFlee
Indicates an entity’s intention or decision to escape or leave a place or situation, typically in a secretive or urgent manner.
- 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_69f76ef7062c819091bfacb7e83aa1e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.