Triple
T30046498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star Wars: X-Wing vs. TIE Fighter |
E763468
|
entity |
| Predicate | allowsPlayerToControl |
P82156
|
FINISHED |
| Object | X-wing fighters |
—
|
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: X-wing fighters | Statement: [Star Wars: X-Wing vs. TIE Fighter, allowsPlayerToControl, X-wing fighters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsPlayerToControl Context triple: [Star Wars: X-Wing vs. TIE Fighter, allowsPlayerToControl, X-wing fighters]
-
A.
canControl
Indicates that one entity has the ability or authority to direct, manage, or influence the behavior or state of another entity.
-
B.
allowsPlayerAction
chosen
Indicates that one entity permits or enables a player to perform a specific action within a system or context.
-
C.
canBeControlledFrom
Indicates that one entity has the ability or authority to operate, direct, or manage another entity remotely or indirectly.
-
D.
hasArtistControl
Indicates that one entity exercises creative or managerial authority over an artist or artistic work.
-
E.
hasCharacterControl
Indicates that one entity has the ability or authority to direct, manipulate, or govern the behavior or state of another entity.
- 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_69f22470a89c8190be7273297c0e0d19 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 29, 2026, 6:54 p.m.