Triple
T29084535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alabama State Route 1 |
E734068
|
entity |
| Predicate | isLargelyUnsigned |
P75662
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Alabama State Route 1, isLargelyUnsigned, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLargelyUnsigned Context triple: [Alabama State Route 1, isLargelyUnsigned, true]
-
A.
isUnsigned
chosen
Indicates that a value, variable, or numeric type is restricted to non-negative numbers and does not include a sign bit for representing negativity.
-
B.
isUnsignedAlong
Indicates that something extends or lies along something else without being formally approved, endorsed, or validated.
-
C.
isSigned
Indicates that an entity has been formally endorsed or authenticated through a signature or signing action.
-
D.
isMostly
Indicates that one entity constitutes the greater part or majority of another entity in amount, extent, or composition.
-
E.
hasSignificant
Indicates that one entity possesses or exhibits a level of importance, impact, or relevance that is notably large or meaningful in relation to another entity or context.
- 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_69f05b0c0f28819086eae6e84f2ae472 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 10:58 a.m.