Triple
T7794683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Road 39 (Florida) |
E180269
|
entity |
| Predicate | functionalRole |
P51151
|
FINISHED |
| Object | regional connector |
—
|
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: regional connector | Statement: [State Road 39 (Florida), functionalRole, regional connector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionalRole Context triple: [State Road 39 (Florida), functionalRole, regional connector]
-
A.
formRole
Indicates that an entity assumes, is assigned, or functions in a particular role within a specified context or structure.
-
B.
effectiveRole
chosen
Indicates the functional role or capacity an entity actually performs or holds in a given context, regardless of its formal or nominal designation.
-
C.
organizationalFunction
Indicates the role, purpose, or primary activity that an organization performs within a broader system or context.
-
D.
role
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
-
E.
canonicalRole
Indicates that an entity holds a standard, primary, or officially recognized role within a particular context 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_69ca827d22208190b4dc5aa680edcf5d |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78a6d88819093f83528fe88b182 |
completed | March 30, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cae9111b2481909684a2d4aa4831c2 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:31 p.m.