Triple
T27361590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Adams (book) |
E685839
|
entity |
| Predicate | coversRelationship |
P171764
|
FINISHED |
| Object | John Adams and Abigail Adams |
—
|
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: John Adams and Abigail Adams | Statement: [John Adams (book), coversRelationship, John Adams and Abigail Adams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversRelationship Context triple: [John Adams (book), coversRelationship, John Adams and Abigail Adams]
-
A.
showsRelationshipWith
Indicates that one entity visually or explicitly presents or demonstrates its connection or association with another entity.
-
B.
subjectRelation
Indicates that one entity stands in a specified relational role or connection to another entity.
-
C.
trackRelationship
Indicates a connection in which one entity monitors, follows, or keeps a record of another entity’s state, behavior, or changes over time.
-
D.
reportsRelationship
Indicates that one entity formally provides information, findings, or status about another entity or situation.
-
E.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
- 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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a28b8ea881908733485374771c51 |
completed | May 3, 2026, 1:19 a.m. |
Created at: April 27, 2026, 11:54 a.m.