Triple
T37051546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wordian age |
E917060
|
entity |
| Predicate | standardUnitFor |
P11666
|
FINISHED |
| Object | middle Permian time correlation |
—
|
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: middle Permian time correlation | Statement: [Wordian age, standardUnitFor, middle Permian time correlation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardUnitFor Context triple: [Wordian age, standardUnitFor, middle Permian time correlation]
-
A.
naturalUnitFor
Indicates that one entity serves as the standard or most appropriate unit of measurement for quantifying another entity.
-
B.
standardUnitRelation
chosen
Indicates a relationship where one unit is defined, measured, or interpreted in terms of a recognized standard unit.
-
C.
baseUnitOf
Indicates that one unit serves as the fundamental reference or standard measurement unit for another derived or related unit.
-
D.
basedUnit
Indicates that one unit is defined in terms of, or derived from, another more fundamental unit.
-
E.
basicUnitOf
Indicates that one entity serves as the fundamental or smallest constituent unit from which the other entity is composed or defined.
- 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_69f76e94d0308190a3f06890e133c88e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: May 3, 2026, 4:14 p.m.