Triple
T3445819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thasos |
E72674
|
entity |
| Predicate | wasKnownInAntiquityFor |
P46173
|
FINISHED |
| Object | gold mines |
—
|
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: gold mines | Statement: [Thasos, wasKnownInAntiquityFor, gold mines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasKnownInAntiquityFor Context triple: [Thasos, wasKnownInAntiquityFor, gold mines]
-
A.
reputationInAntiquity
chosen
Indicates the reputation or standing an entity had during ancient times.
-
B.
ancientNameOf
Indicates that one entity is the historical or ancient name by which the other entity was formerly known.
-
C.
countryDuringAntiquity
Indicates that an entity functioned as a country or political territory specifically during the historical period of antiquity.
-
D.
associatedWithAncientEmpire
Indicates that one entity has a historical, cultural, political, or geographic connection or affiliation with an ancient empire.
-
E.
ancientCity
Indicates that the subject is a historically old or long-established city, typically originating from ancient times.
- 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_69ad85b05c848190b7a28ceec2bd7b74 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adba2cc3048190ab1385699387df8d |
completed | March 8, 2026, 6:04 p.m. |
| PD | Predicate disambiguation | batch_69adae0255b48190a9069f7871c7a012 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.