Triple
T5821424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trans-Alaska Pipeline Authorization Act |
E129116
|
entity |
| Predicate | relatedResource |
P63982
|
FINISHED |
| Object | crude oil |
—
|
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: crude oil | Statement: [Trans-Alaska Pipeline Authorization Act, relatedResource, crude oil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedResource Context triple: [Trans-Alaska Pipeline Authorization Act, relatedResource, crude oil]
-
A.
associatedWithResource
chosen
Indicates a relationship in which an entity is linked or connected to a particular resource, such that the resource is relevant or applicable to that entity.
-
B.
relatedTo
Indicates a general, non-specific relationship or association exists between two entities.
-
C.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
D.
relatedService
Indicates that one service is connected or associated with another service in a relevant or dependent way.
-
E.
targetResource
Indicates that one entity designates another entity as the specific resource or object toward which an action, request, or operation is directed.
- 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_69c0084869e881908d7859492183ca7b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0333fdd7081908d829265caa2ac11 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:53 p.m.