Triple
T20350952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nowhere to Hide |
E496005
|
entity |
| Predicate | hasOpponentsAs |
P116426
|
FINISHED |
| Object | pursuers |
—
|
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: pursuers | Statement: [Nowhere to Hide, hasOpponentsAs, pursuers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpponentsAs Context triple: [Nowhere to Hide, hasOpponentsAs, pursuers]
-
A.
consideredOpponentsAs
Indicates that one entity regarded or treated another entity as an opponent or adversary.
-
B.
hasOpposingSide
Indicates that one entity possesses or is associated with another entity that lies on the opposite or facing side relative to a reference orientation or boundary.
-
C.
associatedOpponent
chosen
Indicates that one entity is recognized or designated as an opponent or adversary associated with another entity in a given context.
-
D.
hasOpposingAgent
Indicates that an entity is opposed or counteracted by another agent in a given context or interaction.
-
E.
hasOpposingTeamsLedBy
Indicates a relationship where a competitive event or context features two opposing teams, each directed or managed by a specific leader.
- 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_69e0b4a3320881909495ae8bc30bc2dc |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6784f8ff48190a070888786f6a989 |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:24 a.m.