Triple
T294218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anatolian languages |
E6057
|
entity |
| Predicate | attestedFrom |
P10386
|
FINISHED |
| Object | early 2nd millennium BCE |
—
|
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: early 2nd millennium BCE | Statement: [Anatolian languages, attestedFrom, early 2nd millennium BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attestedFrom Context triple: [Anatolian languages, attestedFrom, early 2nd millennium BCE]
-
A.
believedBy
Indicates that a particular proposition, statement, or entity is held to be true or accepted as real by a specified believer.
-
B.
knownFrom
Indicates that one entity is aware of, has learned about, or recognizes another entity through a specified source, context, or medium.
-
C.
establishedFrom
Indicates that something was created, founded, or formed starting from a specified source, origin, or prior entity.
-
D.
confirmedBy
Indicates that one entity validates, approves, or verifies the truth, accuracy, or occurrence of another entity or event.
-
E.
notableWitness
Indicates that one entity is a significant or prominent witness to an event, action, or situation involving another entity.
- 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2e9e273f88190ac5355d1310376ed |
completed | Feb. 28, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69a2e9368894819093eeae4347dfcc5a |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2e9e0d85c8190ae52662d83ea67fe |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.