Triple
T6687625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ida Green |
E152137
|
entity |
| Predicate | notableCoupleWith |
P35186
|
FINISHED |
| Object | Cecil H. Green |
—
|
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: Cecil H. Green | Statement: [Ida Green, notableCoupleWith, Cecil H. Green]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCoupleWith Context triple: [Ida Green, notableCoupleWith, Cecil H. Green]
-
A.
notableCouple
chosen
Indicates that two entities are widely recognized or documented as a couple in a notable or significant relationship.
-
B.
marriedToNotablePerson
Indicates that a person is legally married to another individual who is widely recognized or notable.
-
C.
spouseNotableFor
Indicates that a person's spouse is recognized or distinguished for a particular achievement, role, or characteristic.
-
D.
notableConsort
Indicates that one entity is a spouse or consort of another who is notable or significant in some recognized context.
-
E.
notableCastPairing
Indicates that two cast members are notably associated with each other in a particular work, such as through a prominent or distinctive joint appearance.
- 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_69c687f9977c819097e7f5ada4fe522e |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cd0fa5188190a23281cb09d98139 |
completed | March 27, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69c6ad0d3c1081908dadff7a6a054123 |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:04 p.m.