Triple
T28758760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederica Vernon |
E731746
|
entity |
| Predicate | opposedMarriageTo |
P138079
|
FINISHED |
| Object | Sir James Martin |
—
|
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: Sir James Martin | Statement: [Frederica Vernon, opposedMarriageTo, Sir James Martin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposedMarriageTo Context triple: [Frederica Vernon, opposedMarriageTo, Sir James Martin]
-
A.
refusedRemarriageTo
Indicates that one entity declined or rejected entering into a subsequent marriage with another entity.
-
B.
failsToMarry
Indicates that an expected or attempted marriage between entities does not successfully occur.
-
C.
preventedMarriageBy
chosen
Indicates that one entity took actions or imposed conditions that stopped or blocked another entity’s intended or potential marriage from occurring.
-
D.
supportsMarriageBetween
Indicates that one entity endorses or is in favor of a marital union between the specified parties.
-
E.
rivalForMarriageOf
Indicates that one entity is a romantic competitor with another entity for the opportunity to marry a specific third 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_69f043ed68a881909e858a06bab7a247 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 28, 2026, 6:10 a.m.