Triple
T8474258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linear A |
E200350
|
entity |
| Predicate | earliestUse |
P55558
|
FINISHED |
| Object | circa 1800 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: circa 1800 BCE | Statement: [Linear A, earliestUse, circa 1800 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestUse Context triple: [Linear A, earliestUse, circa 1800 BCE]
-
A.
historicalPeriodOfFirstUse
chosen
Indicates the historical time period during which something was first used or came into use.
-
B.
firstHistoricalUse
Indicates that the subject entity represents the earliest known or recorded instance of the object entity being used or occurring in history.
-
C.
locationOfEarlyUse
Indicates the place where something was first or among the earliest instances to be used or applied.
-
D.
firstWidelyUsedDuring
Indicates that something (such as a concept, technology, or practice) came into its first period of broad or widespread use during a specified time or era.
-
E.
earliestWellKnownExample
Indicates that one entity is the earliest well-known example or instance of the other entity.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4f7328481909ad19bcf8d182022 |
completed | March 31, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69cbd104250c8190b4c499dcc9937494 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.