Triple
T25250777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archaeological Site of Troy |
E632734
|
entity |
| Predicate | hasDurationOfOccupation |
P16740
|
FINISHED |
| Object | over 4000 years |
—
|
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: over 4000 years | Statement: [Archaeological Site of Troy, hasDurationOfOccupation, over 4000 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDurationOfOccupation Context triple: [Archaeological Site of Troy, hasDurationOfOccupation, over 4000 years]
-
A.
periodOfContinuousInhabitation
chosen
Indicates a span of time during which a place is continuously inhabited without interruption.
-
B.
hasEvidenceOfOccupationSince
Indicates that there is evidence showing an entity has been occupied continuously or intermittently since a specified point in time.
-
C.
wasOccupiedDuring
Indicates that an entity was under the control, presence, or use of another entity throughout a specified time period.
-
D.
occupationDuration
Indicates the length of time an entity holds or has held a particular occupation or role.
-
E.
residencePeriod
Indicates the length of time an entity resides or has resided at a particular location.
- 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_69e75a8fdd3881909ba0b05aa5da92a7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4808b8ab08190b48cca8408c88bdf |
completed | May 1, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:11 p.m.