Triple
T6915880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deadhorse Airport |
E160049
|
entity |
| Predicate | servesWorkers |
P14200
|
FINISHED |
| Object | Prudhoe Bay oil field workers |
—
|
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: Prudhoe Bay oil field workers | Statement: [Deadhorse Airport, servesWorkers, Prudhoe Bay oil field workers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesWorkers Context triple: [Deadhorse Airport, servesWorkers, Prudhoe Bay oil field workers]
-
A.
representsWorkersOf
Indicates a relationship where one entity denotes or stands for the workers associated with another entity.
-
B.
servesUsers
chosen
Indicates that an entity provides services, functionality, or benefits to one or more users.
-
C.
servesUnder
Indicates that one entity works in a subordinate role under the authority, command, or supervision of another entity.
-
D.
servesUsersFrom
Indicates that an entity provides services or resources to users originating from or associated with a specified source or location.
-
E.
involvesWorkers
Indicates that an event, process, or situation includes workers as active participants or affected parties.
- 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_69c6883ab1008190a07129ff06f625d9 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9dec058819094d1913a1e5218c0 |
completed | March 27, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b93d688190a297244ce81b67ac |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:26 p.m.