Triple
T15213883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fanning Springs, Florida |
E363587
|
entity |
| Predicate | springMagnitude |
P43622
|
FINISHED |
| Object | first-magnitude spring |
—
|
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: first-magnitude spring | Statement: [Fanning Springs, Florida, springMagnitude, first-magnitude spring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: springMagnitude Context triple: [Fanning Springs, Florida, springMagnitude, first-magnitude spring]
-
A.
springType
chosen
Indicates the specific kind or category of spring associated with an entity (e.g., coil, leaf, torsion).
-
B.
magnitudeScale
Indicates the scale or measurement system used to quantify the magnitude or intensity of something.
-
C.
exampleMagnitude
Indicates a relationship where one entity serves as a representative or typical instance that illustrates the scale, size, or intensity (magnitude) of another entity or quantity.
-
D.
hasMultipleSprings
Indicates that an entity possesses more than one spring as part of its structure or mechanism.
-
E.
tunedMassDamperWeight_tonnes
Indicates the weight, measured in metric tonnes, of the tuned mass damper used in a structure or system.
- 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0076e4348819091fa91c1562e7c5c |
completed | April 15, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69deca8479188190b2e5d3bc708d7d07 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:11 a.m.