Triple
T7844473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florida State Road |
E181888
|
entity |
| Predicate | signFeatures |
P51216
|
FINISHED |
| Object | outline of the state of Florida |
—
|
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: outline of the state of Florida | Statement: [Florida State Road, signFeatures, outline of the state of Florida]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signFeatures Context triple: [Florida State Road, signFeatures, outline of the state of Florida]
-
A.
signatureFeature
chosen
Indicates that one entity is a defining or characteristic feature that distinctly identifies or typifies another entity.
-
B.
signType
Indicates the specific category or kind of sign involved in the relationship or action.
-
C.
signPattern
Indicates a specific arrangement or sequence of positive, negative, or zero signs associated with a set of values or components.
-
D.
signature
Indicates that one entity has provided an official or personal signed endorsement, authorization, or acknowledgment on or for another entity.
-
E.
signatureImage
Indicates that an entity has an associated image that visually represents its signature.
- 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_69ca8285d6488190a95d4c02d7354b53 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb163c72248190b53bc53980e8ac0f |
completed | March 31, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69cae91e98988190abd4ece75932c589 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:48 p.m.