Triple
T34850535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. numbered business routes |
E1004587
|
entity |
| Predicate | typicalSignText |
P74189
|
FINISHED |
| Object | Business |
—
|
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: Business | Statement: [U.S. numbered business routes, typicalSignText, Business]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSignText Context triple: [U.S. numbered business routes, typicalSignText, Business]
-
A.
typicalSymbol
Indicates that something serves as a characteristic or commonly recognized symbol representing something else.
-
B.
signType
chosen
Indicates the specific category or kind of sign involved in the relationship or action.
-
C.
showsSignOf
Indicates that one entity exhibits evidence, symptoms, or characteristics suggesting the presence or occurrence of another entity, condition, or state.
-
D.
signsWith
Indicates that one entity formally enters into or endorses an agreement, document, or commitment together with another entity as a co-signer.
-
E.
commonSign
Indicates that multiple entities share the same sign, symbol, or indicator in common.
- 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_69f76dba76f0819090643cba102c41ec |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.