Triple
T30675177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Axel Alonso |
E780890
|
entity |
| Predicate | oversawTitle |
P178073
|
FINISHED |
| Object | Avengers vs. X-Men |
—
|
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: Avengers vs. X-Men | Statement: [Axel Alonso, oversawTitle, Avengers vs. X-Men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oversawTitle Context triple: [Axel Alonso, oversawTitle, Avengers vs. X-Men]
-
A.
oversawWorksOf
chosen
Indicates that one entity supervised, managed, or had authoritative responsibility over the work or creations produced by another entity.
-
B.
oversawDocument
Indicates that one entity supervised, managed, or had responsibility for the creation, handling, or review of a document associated with another entity.
-
C.
oversawPolicy
Indicates that one entity had supervisory or managerial responsibility for the creation, implementation, or maintenance of a policy affecting another entity or domain.
-
D.
oversee
Indicates having responsibility for supervising, directing, or managing the actions or work of another entity.
-
E.
oversawEvent
Indicates that an entity had supervisory or managerial responsibility for the planning, execution, or overall conduct of an event.
- 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_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 29, 2026, 8:32 p.m.