Triple
T28968955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benatar |
E734217
|
entity |
| Predicate | temporarilyOperatedBy |
P15084
|
FINISHED |
| Object | Thor |
—
|
NE NERFINISHED |
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: Thor | Statement: [Benatar, temporarilyOperatedBy, Thor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporarilyOperatedBy Context triple: [Benatar, temporarilyOperatedBy, Thor]
-
A.
formerlyOperatedBy
chosen
Indicates that an entity was previously operated or managed by another entity, but is no longer under that operation.
-
B.
laterOperatedUnder
Indicates that an entity, after an earlier period, was subsequently managed, controlled, or conducted under a different name, organization, framework, or operational context.
-
C.
operatedAs
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
-
D.
oftenOperatedBy
Indicates that an entity is frequently or typically operated, controlled, or run by another entity.
-
E.
alsoOperatedBy
Indicates that an entity is additionally operated or managed by another operator, alongside any primary or other operators.
- 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 9:04 a.m.