Triple
T24513770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaston de Montgomery |
E606300
|
entity |
| Predicate | opponentInJoust |
P18835
|
FINISHED |
| Object | Henry II of France |
—
|
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: Henry II of France | Statement: [Gaston de Montgomery, opponentInJoust, Henry II of France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentInJoust Context triple: [Gaston de Montgomery, opponentInJoust, Henry II of France]
-
A.
opponentInCase
Indicates that two parties are on opposing sides in the same legal case or proceeding.
-
B.
battleOpponent
chosen
Indicates that two entities are engaged in or designated as opponents in a battle or combat scenario.
-
C.
opponentInScenario
Indicates that one entity is an adversary or rival of another within a specific scenario, context, or situation.
-
D.
facedOpponent
Indicates that one entity directly confronted or competed against another as an opponent in a contest, conflict, or challenge.
-
E.
opponentTitle
Indicates that the object is the formal title or designation held by an opponent in a competitive or adversarial context.
- 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_69e2c4c725148190a4e41577c5cb409c |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:24 a.m.