Triple
T4505418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boardwalk Empire |
E101319
|
entity |
| Predicate | pilotRuntime |
P57045
|
FINISHED |
| Object | 73 minutes |
—
|
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: 73 minutes | Statement: [Boardwalk Empire, pilotRuntime, 73 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pilotRuntime Context triple: [Boardwalk Empire, pilotRuntime, 73 minutes]
-
A.
pilotRun
Indicates that an entity conducts or participates in a preliminary or trial implementation of a process, system, or project to test and evaluate it before full-scale deployment.
-
B.
pilotDirector
Indicates that one entity serves as the director of the pilot episode or initial installment of another entity (such as a series or project).
-
C.
pilotHijacker
Indicates that the subject is a pilot who hijacks, or has hijacked, an aircraft.
-
D.
testPilot
Indicates that an entity serves as a pilot responsible for testing and evaluating aircraft or related flight systems.
-
E.
pilotFormat
Indicates that one entity serves as the primary or reference format used to guide or standardize how another entity is structured, presented, or executed.
- F. None of above. chosen
Provenance (4 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_69bd43d175248190894dc58b5b395c26 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd56ff78748190bb667e70c69dc817 |
completed | March 20, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69bd5218afb4819087c99e0a1f22e137 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b3e4c88190a7ade3d0ed0ab606 |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:01 p.m.