Triple
T2615576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Sounion |
E58879
|
entity |
| Predicate | usedInAntiquityAs |
P2417
|
FINISHED |
| Object | strategic lookout point |
—
|
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: strategic lookout point | Statement: [Cape Sounion, usedInAntiquityAs, strategic lookout point]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInAntiquityAs Context triple: [Cape Sounion, usedInAntiquityAs, strategic lookout point]
-
A.
historicallyUsedFor
chosen
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
-
B.
ancientNameOf
Indicates that one entity is the historical or ancient name by which the other entity was formerly known.
-
C.
traditionallyUsedBy
Indicates that something has been customarily or historically used by a particular person, group, or culture over time.
-
D.
widelyUsedIn
Indicates that something is commonly or extensively utilized within a particular context, domain, or group.
-
E.
historicallyBorneBy
Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
- 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_69ab4ac444dc819099614e534dd6021f |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd89325308190985598373eb0d296 |
completed | March 7, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69abd80cd7fc81909e9696db2919129f |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.