Triple
T2948028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Route 7 (Virginia) |
E79549
|
entity |
| Predicate | functionalClass |
P5621
|
FINISHED |
| Object | primary state highway |
—
|
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: primary state highway | Statement: [State Route 7 (Virginia), functionalClass, primary state highway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionalClass Context triple: [State Route 7 (Virginia), functionalClass, primary state highway]
-
A.
definesClassification
Indicates that one entity specifies or establishes the classification or category to which another entity belongs.
-
B.
serviceClass
chosen
Indicates the classification or category of service associated with or provided by an entity in the relationship.
-
C.
publicFunction
Indicates that a function or method is accessible from outside its defining scope, module, or class (i.e., it has public visibility).
-
D.
computationalClass
Indicates that two entities share the same computational complexity class or that one entity is categorized within a specified computational complexity class.
-
E.
typicalFunction
Indicates that something serves as the usual or characteristic function or role of an 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_69ad8b1089588190b74d9e2505e45762 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad98b6cab88190b4dee7e5ec9347e5 |
completed | March 8, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69ad960a70ac8190816b5ae3e8631031 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:57 p.m.