Triple
T11707960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assos |
E278295
|
entity |
| Predicate | TempleOfAthenaBuiltInCentury |
P93743
|
FINISHED |
| Object | 6th century BCE |
—
|
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: 6th century BCE | Statement: [Assos, TempleOfAthenaBuiltInCentury, 6th century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TempleOfAthenaBuiltInCentury Context triple: [Assos, TempleOfAthenaBuiltInCentury, 6th century BCE]
-
A.
affirmedInCentury
Indicates that a statement, belief, or status was formally confirmed or upheld during a specified century.
-
B.
amphitheatreBuiltUnder
Indicates that an amphitheatre was constructed during the rule, authority, or administration of a specified person or governing entity.
-
C.
hasAcropolis
Indicates that one entity possesses, contains, or is associated with an acropolis (a fortified high area or citadel).
-
D.
locatedInAncientCity
Indicates that an entity is situated within the boundaries or domain of an ancient city.
-
E.
containsBuildingFromCentury
chosen
Indicates that a location or area includes at least one building that originates from a specified century.
- 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a49de0388190a063739426bf90e8 |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a7d483081909c2a101087515d74 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.