Triple
T37143311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 49 CFR Part 382 |
E920173
|
entity |
| Predicate | incorporatesByReference |
P126159
|
FINISHED |
| Object | 49 CFR Part 40 |
—
|
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: 49 CFR Part 40 | Statement: [49 CFR Part 382, incorporatesByReference, 49 CFR Part 40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incorporatesByReference Context triple: [49 CFR Part 382, incorporatesByReference, 49 CFR Part 40]
-
A.
incorporatedByReference
chosen
Indicates that one document, provision, or element is made part of another by referring to it rather than reproducing its full content.
-
B.
incorporatedBy
Indicates that an entity was formally created, organized, or established as a legal corporation by another entity.
-
C.
incorporatesDefinitionFrom
Indicates that one entity’s definition includes or is derived from the definition of another entity.
-
D.
incorporatedFrom
Indicates that one entity was formed, established, or legally created by deriving or transforming from another pre-existing entity.
-
E.
incorporatesElementsFrom
Indicates that one entity includes or integrates components, features, or aspects derived from 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_69f76e9e9d008190a250b0387c992c74 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:15 p.m.