Triple
T5002357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 摺鉢山 |
E112402
|
entity |
| Predicate | 地質時代 |
P1327
|
FINISHED |
| Object | 第四紀火山 |
—
|
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: 第四紀火山 | Statement: [摺鉢山, 地質時代, 第四紀火山]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 地質時代 Context triple: [摺鉢山, 地質時代, 第四紀火山]
-
A.
geologicalAge
chosen
Indicates the time period in Earth's geological history during which an entity (such as a rock, fossil, or formation) originated or was formed.
-
B.
locatedInGeologicPast
Indicates that something existed or occurred in a specific place during a past geologic time period.
-
C.
geologicalRange
Indicates the span of geological time during which an entity (such as a taxon or formation) is known to have existed or been present.
-
D.
geologicalSystem
Indicates that one entity is a geological system (e.g., rock units, structures, or processes forming a coherent geologic framework) associated with or characterizing the other entity.
-
E.
geologicAgeRelativeTo
Indicates the relative chronological order between two geologic ages, specifying which one is older or younger without giving an absolute date.
- 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_69bd4433d0b08190877e83959ef40d81 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7472a1dc8190942f568a81fdd961 |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd714aee2481908fb0dd5fa2daf3a1 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:34 p.m.