Triple
T8230057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hisarlik |
E192268
|
entity |
| Predicate | hasArchaeologicalLayer |
P31670
|
FINISHED |
| Object | Troy V |
E112533
|
NE 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: Troy V | Statement: [Hisarlik, hasArchaeologicalLayer, Troy V]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Troy V Context triple: [Hisarlik, hasArchaeologicalLayer, Troy V]
-
A.
Troyan
Troyan is a town in central Bulgaria, known for its proximity to the Balkan Mountains, traditional crafts, and the nearby Troyan Monastery.
-
B.
TROA
TROA is a water management agreement that governs the operation and allocation of flows in the Truckee River system in California and Nevada.
-
C.
Troy
Troy is a small city in southeastern Alabama known for being the home of Troy University and its vibrant college-town atmosphere.
-
D.
Troy
chosen
Troy is the legendary ancient city in Asia Minor that was the focal point of the Trojan War in Greek and Roman mythology.
-
E.
Troy
Troy is a masculine given name of ancient origin, famously borne by former NFL quarterback Troy Aikman.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca82db5b90819085d1ad7c2e27bfcc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7802417c81908837c31136c41a5c |
completed | March 31, 2026, 7:30 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd67ec97348190a1ae7fc8d30af838 |
completed | April 1, 2026, 6:46 p.m. |
Created at: March 30, 2026, 5:46 p.m.