Triple
T25860035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homeric geography |
E651454
|
entity |
| Predicate | includesDebatesOn |
P57127
|
FINISHED |
| Object | location of Troy |
—
|
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: location of Troy | Statement: [Homeric geography, includesDebatesOn, location of Troy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesDebatesOn Context triple: [Homeric geography, includesDebatesOn, location of Troy]
-
A.
hasDebateAround
Indicates that there is ongoing discussion, disagreement, or controversy surrounding the referenced entity or topic.
-
B.
areDebatesOf
Indicates that the subject entities are debates that concern, involve, or are associated with the object entities.
-
C.
hasLongTermDebateOn
Indicates that there is an ongoing, extended period of discussion, disagreement, or argument concerning a particular topic or issue.
-
D.
debatedWithin
chosen
Indicates that something is discussed or argued about within a particular group, context, or domain.
-
E.
hasDebate
Indicates that there is a formal discussion or argument between entities, typically presenting opposing viewpoints on a topic.
- 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_69e7ab3a199c81909227cb964cacfe24 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: April 22, 2026, 8:05 a.m.