Triple
T904770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lesbos |
E19521
|
entity |
| Predicate | inhabitedSince |
P22541
|
FINISHED |
| Object | prehistoric times |
—
|
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: prehistoric times | Statement: [Lesbos, inhabitedSince, prehistoric times]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inhabitedSince Context triple: [Lesbos, inhabitedSince, prehistoric times]
-
A.
historicallyInhabitedBy
Indicates that a place or region was inhabited by a particular group or population during some period in the past.
-
B.
inhabitedBy
Indicates that a place or location is lived in or occupied by a particular individual, group, or species.
-
C.
firstDomesticatedIn
Indicates the place or context where an entity was initially brought under human control or cultivation for the first time.
-
D.
earliestKnownAncestor
Indicates that one entity is the most distant (oldest) known ancestor in the lineage of another entity.
-
E.
hasPermanentHumanPopulation
Indicates that an entity consistently hosts a stable, long-term community of human residents rather than only temporary or transient occupants.
- 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_69a4939e889c8190ac148b3ac1a7f90b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3bcad2481908b83575b2fb80d14 |
completed | March 1, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69a4b28ff5948190982c4439eadf9d87 |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b3bab5788190a62a0e23a698f7c7 |
completed | March 1, 2026, 9:46 p.m. |
Created at: March 1, 2026, 7:39 p.m.