Triple
T36925692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fountain Formation |
E913336
|
entity |
| Predicate | subdivisionOfPeriod |
P8382
|
FINISHED |
| Object | Pennsylvanian subperiod |
—
|
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: Pennsylvanian subperiod | Statement: [Fountain Formation, subdivisionOfPeriod, Pennsylvanian subperiod]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subdivisionOfPeriod Context triple: [Fountain Formation, subdivisionOfPeriod, Pennsylvanian subperiod]
-
A.
partOfWorkPeriod
Indicates that a specific time span is contained within, and belongs to, a larger defined work period.
-
B.
hasSubPeriod
chosen
Indicates that a time period is composed of or contains another, more specific time period as a subordinate part.
-
C.
subdividedBy
Indicates that something is divided into smaller parts or sections by another entity or criterion.
-
D.
minorUnitSubdivisions
Indicates that one administrative or organizational unit is subdivided into smaller, subordinate units.
-
E.
continuedIntoPeriod
Indicates that an action, state, or relationship that began earlier persisted without interruption into a specified later time period.
- 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_69f76e896c988190880c130e01303dd4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fdcfdc3c81908c5ee5bcbd45a63c |
completed | May 5, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.