Triple
T30674244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | War Dogs |
E780869
|
entity |
| Predicate | operationalStatusInMCU |
P5870
|
FINISHED |
| Object | active |
—
|
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: active | Statement: [War Dogs, operationalStatusInMCU, active]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalStatusInMCU Context triple: [War Dogs, operationalStatusInMCU, active]
-
A.
MCUStatus
Indicates the operational or health state of a microcontroller unit (MCU) at a given time.
-
B.
statusInMCU
Indicates the role or condition an entity holds within the Marvel Cinematic Universe continuity.
-
C.
operatingStatus
chosen
Indicates whether an entity is currently functioning, active, or in service versus inactive, closed, or out of service.
-
D.
operatorStatus
Indicates the current operational state or condition of an operator (e.g., active, inactive, or in error).
-
E.
maintenanceStatus
Indicates the current state or condition of an entity with respect to its maintenance activities, such as whether it is pending, in progress, completed, or overdue.
- 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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff6fba1a5c8190a660279a6271d785 |
completed | May 9, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69ff6f59388c8190a7d6ab7bc7705bc0 |
completed | May 9, 2026, 5:31 p.m. |
Created at: April 29, 2026, 8:32 p.m.