Triple
T28841172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 493 |
E728317
|
entity |
| Predicate | isNumberReserved |
P99271
|
FINISHED |
| Object | no specific reservation known |
—
|
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: no specific reservation known | Statement: [Interstate 493, isNumberReserved, no specific reservation known]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNumberReserved Context triple: [Interstate 493, isNumberReserved, no specific reservation known]
-
A.
isReserved
chosen
Indicates that something has been set aside or booked in advance for a particular person, purpose, or time, and is not available for general use.
-
B.
isClassicNumber
Indicates that a number belongs to a traditionally recognized or canonical set of numbers defined as "classic" within a given context.
-
C.
mayBeReservedBy
Indicates that an entity is eligible or allowed to be reserved by another entity, without asserting that the reservation has actually occurred.
-
D.
hasNumberInStructure
Indicates that an entity’s structure includes or contains a specific numerical value or component.
-
E.
isWellKnownNumberFrom
Indicates that a number is widely recognized or famous within the context or domain specified by the source entity.
- 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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 6:40 a.m.