Triple
T2276853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Car Assessment Program |
E50790
|
entity |
| Predicate | informationAvailableThrough |
P17720
|
FINISHED |
| Object | NHTSA website |
—
|
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: NHTSA website | Statement: [New Car Assessment Program, informationAvailableThrough, NHTSA website]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: informationAvailableThrough Context triple: [New Car Assessment Program, informationAvailableThrough, NHTSA website]
-
A.
providesInformationIn
chosen
Indicates that one entity supplies or conveys information within or through another entity or context.
-
B.
accessibleFrom
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
-
C.
usesInformationSources
Indicates that an entity relies on or consults specified information sources to perform actions, make decisions, or obtain knowledge.
-
D.
textAvailableAt
Indicates that a specific piece of text can be accessed or obtained at a given location, source, or resource.
-
E.
hasInformationService
Indicates that one entity provides, operates, or is associated with an information-related service for 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_69a88b05910c8190a9a2b1ff230c85f9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc1ee22988190b7fa28b0b62e8668 |
completed | March 7, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69abbdb9aa3c819088d0316c5269a1c2 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.