Triple
T1007959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth lithosphere |
E21755
|
entity |
| Predicate | averageAgeOceanic |
P23543
|
FINISHED |
| Object | less than about 200 million years |
—
|
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: less than about 200 million years | Statement: [Earth lithosphere, averageAgeOceanic, less than about 200 million years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: averageAgeOceanic Context triple: [Earth lithosphere, averageAgeOceanic, less than about 200 million years]
-
A.
isMostlyOceanic
Indicates that something consists predominantly of ocean or sea areas rather than land.
-
B.
recognizedAsOceanSince
Indicates that an entity has been officially classified or acknowledged as an ocean starting from a specified point in time.
-
C.
oceanicPortion
Indicates that one entity is a part or segment of an ocean or oceanic area in relation to another entity.
-
D.
oceanBasin
Indicates a relationship where a geographic or marine feature is located within, or is part of, a specific ocean basin.
-
E.
hasOcean
Indicates that a geographic region, country, or landmass is bordered by or directly adjacent to a particular ocean.
- 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_69a493c53e648190ae8cb76c433fd9a7 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7f4c66c8190b6098fb72c1465a3 |
completed | March 1, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69a4b7203124819091de68cba5f731c1 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b7f2d1b081908eb2df54e91c8c1d |
completed | March 1, 2026, 10:04 p.m. |
Created at: March 1, 2026, 7:41 p.m.