Triple
T37625057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michigan meridian |
E936181
|
entity |
| Predicate | hasAssociatedBaseline |
P168905
|
FINISHED |
| Object | Michigan baseline |
—
|
NE NERFINISHED |
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: Michigan baseline | Statement: [Michigan meridian, hasAssociatedBaseline, Michigan baseline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedBaseline Context triple: [Michigan meridian, hasAssociatedBaseline, Michigan baseline]
-
A.
hasBaselineLength
Indicates that one entity has a specified baseline length measurement in relation to another entity or reference.
-
B.
usesBaseline
Indicates that one entity relies on or applies another entity as a reference baseline for comparison, measurement, or evaluation.
-
C.
providesBaseline
chosen
Indicates that one entity supplies a reference standard or starting level against which another entity’s performance, state, or changes are measured.
-
D.
hasHistoricBasisIn
Indicates that something is grounded in, derived from, or justified by historical events, practices, or precedents.
-
E.
hasBaseDate
Indicates that an entity is associated with a specific reference or starting date used as the basis for related calculations, schedules, or validity periods.
- 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_69f76ed24820819081bafd36e9088701 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
Created at: May 3, 2026, 4:18 p.m.