Triple
T18588982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | conquest of Cybertron |
E454308
|
entity |
| Predicate | hasOppositionGoal |
P132694
|
FINISHED |
| Object | defense of Cybertronian freedom |
—
|
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: defense of Cybertronian freedom | Statement: [conquest of Cybertron, hasOppositionGoal, defense of Cybertronian freedom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOppositionGoal Context triple: [conquest of Cybertron, hasOppositionGoal, defense of Cybertronian freedom]
-
A.
ownGoalBy
Indicates that a goal was accidentally scored against a team by the specified player (i.e., the player scored an own goal).
-
B.
numberOfGoals
Indicates the total count of goals scored or achieved by an entity in a given context.
-
C.
officialGoal
Indicates that something is the formally designated or institutionally recognized objective or target of an entity.
-
D.
ownGoalBeneficiaryTeam
Indicates the team that gains the scoring benefit when an own goal is committed against it.
-
E.
penaltyScoredBy
Indicates that a penalty (typically in a game or sport) was successfully converted or scored by a particular participant.
- F. None of above. chosen
Provenance (4 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e545b3e564819088e60fc25d1976f0 |
completed | April 19, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:44 a.m.