Triple
T6050159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Jersey State Highway System |
E134769
|
entity |
| Predicate | includesFunctionalClass |
P53933
|
FINISHED |
| Object | freeway |
—
|
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: freeway | Statement: [New Jersey State Highway System, includesFunctionalClass, freeway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesFunctionalClass Context triple: [New Jersey State Highway System, includesFunctionalClass, freeway]
-
A.
usesClass
Indicates that one entity makes use of, depends on, or is implemented using a particular class in its structure or behavior.
-
B.
classificationIncludes
chosen
Indicates that a broader classification category encompasses or contains a specified subclass, member, or element within its scope.
-
C.
containsFunction
Indicates that one entity includes, defines, or provides the implementation of a particular function.
-
D.
includesInfraclass
Indicates that one entity is classified as belonging to a specific infraclass within a taxonomic hierarchy.
-
E.
includesAbstract
Indicates that one entity contains or incorporates the abstract or summary section of another 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_69c00876a69881908088a2626d3b2666 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056f4f84c8190a7e2416d81b3554c |
completed | March 22, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69c049edc6f0819092ca620d9073ad26 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:09 p.m.