Triple
T3600499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scillus |
E76242
|
entity |
| Predicate | inhabitedDuring |
P50149
|
FINISHED |
| Object | Classical period of ancient Greece |
—
|
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: Classical period of ancient Greece | Statement: [Scillus, inhabitedDuring, Classical period of ancient Greece]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inhabitedDuring Context triple: [Scillus, inhabitedDuring, Classical period of ancient Greece]
-
A.
inhabitedSince
Indicates that a place has been continuously or initially occupied or lived in by someone or something starting from a specified time.
-
B.
historicallyInhabitedBy
Indicates that a place or region was inhabited by a particular group or population during some period in the past.
-
C.
inhabitedBy
Indicates that a place or location is lived in or occupied by a particular individual, group, or species.
-
D.
livedDuring
Indicates that the subject existed or was alive at some point within the time period or lifespan associated with the object.
-
E.
periodOfContinuousInhabitation
Indicates a span of time during which a place is continuously inhabited without interruption.
- F. None of above. chosen
Provenance (4 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_69ad85d93dcc819094fba90cf70f4996 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc1a1e8c48190a28ea3ddfe8c4e54 |
completed | March 8, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69adb83b66708190bb9d2f23d6fd308e |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb9261a948190b67f6c6ac0dae2e9 |
completed | March 8, 2026, 6 p.m. |
Created at: March 8, 2026, 3:22 p.m.