Triple
T9718747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Badarian culture |
E235407
|
entity |
| Predicate | timeInferredFrom |
P30540
|
FINISHED |
| Object | radiocarbon dating |
—
|
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: radiocarbon dating | Statement: [Badarian culture, timeInferredFrom, radiocarbon dating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInferredFrom Context triple: [Badarian culture, timeInferredFrom, radiocarbon dating]
-
A.
timePeriodImplied
chosen
Indicates that a time period is inferred or implied by context rather than being explicitly specified.
-
B.
timeOfAppearance
Indicates the specific time at which an entity or event becomes visible, present, or first occurs.
-
C.
formedAt
Indicates the time or date at which an entity was created, established, or came into existence.
-
D.
timeStartApprox
Indicates that the associated event or state begins at an approximate, rather than exact, point in time.
-
E.
inceptionTime
Indicates the specific point in time when an entity, event, or relationship begins or is first established.
- 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_69ca84d0123c819096f9dc3b6abb0881 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9e3ea61081908a5671fc5be9a738 |
completed | April 1, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69cd03bfeca08190924fca43aaa9c10f |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:20 p.m.