Triple
T32143707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strongyle |
E820970
|
entity |
| Predicate | inAncientSource |
P142914
|
FINISHED |
| Object | classical Greek authors |
—
|
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 Greek authors | Statement: [Strongyle, inAncientSource, classical Greek authors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inAncientSource Context triple: [Strongyle, inAncientSource, classical Greek authors]
-
A.
linkedToAncientSource
chosen
Indicates that one entity is connected or traceable to an ancient source, origin, or reference.
-
B.
discoveredInAntiquity
Indicates that something was found, identified, or recognized during ancient historical times rather than in the modern era.
-
C.
isAncient
Indicates that the entity existed or originated in a very distant past, typically far earlier than the commonly referenced historical period.
-
D.
ancientLanguages
Indicates that the related entities are languages that originated in and were used during ancient historical periods.
-
E.
ancientAttributionBy
Indicates that an entity is credited or assigned to another entity based on ancient or historical sources rather than modern evidence.
- 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_69f3490520d081909b2f1271dab75faa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b9b17d908190a6bfa2f8b5402f1e |
completed | May 3, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:31 a.m.