Triple
T36411479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act IV |
E896890
|
entity |
| Predicate | hasPositionInPlay |
P11751
|
FINISHED |
| Object | fourth act |
—
|
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: fourth act | Statement: [Act IV, hasPositionInPlay, fourth act]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPositionInPlay Context triple: [Act IV, hasPositionInPlay, fourth act]
-
A.
isInPlayBy
Indicates that an entity is currently active or participating within a game, scenario, or context as a result of actions taken by a specific agent or player.
-
B.
playsInPosition
chosen
Indicates that an entity (typically a player) performs or operates in a specific role or position within a game, sport, or activity.
-
C.
hasPositionInPlayoffs
Indicates that an entity holds a specific rank or standing within a playoff competition or bracket.
-
D.
activeInLeague
Indicates that an entity (such as a team or player) is currently participating in or belongs to a particular league.
-
E.
hasPhaseOfPlay
Indicates a relationship where a broader game or activity includes or is associated with a specific phase or segment of play.
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff84df768c81908c65a1a7e33103ad |
completed | May 9, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69ff848d0af881908ee42c27a58af47e |
completed | May 9, 2026, 7:01 p.m. |
Created at: May 3, 2026, 4:10 p.m.