Triple
T35854138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 12 Lunar Module Intrepid |
E1036448
|
entity |
| Predicate | matedWith |
P183902
|
FINISHED |
| Object | Apollo 12 Command and Service Module Yankee Clipper |
—
|
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: Apollo 12 Command and Service Module Yankee Clipper | Statement: [Apollo 12 Lunar Module Intrepid, matedWith, Apollo 12 Command and Service Module Yankee Clipper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matedWith Context triple: [Apollo 12 Lunar Module Intrepid, matedWith, Apollo 12 Command and Service Module Yankee Clipper]
-
A.
bondedWith
Indicates that two entities are joined by a strong, enduring connection or attachment, whether emotional, social, or structural.
-
B.
marriedBy
Indicates that one entity is the officiant or authority who performs and formalizes the marriage of another entity.
-
C.
marriedIn
Indicates that two entities entered into a marital relationship at a specific place or within a particular jurisdiction.
-
D.
marriedInto
Indicates that one entity became connected to another’s family or group through marriage, rather than by birth or prior membership.
-
E.
marriedOn
Indicates that a marriage event took place on a specific date for the related entities.
- 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_69f76e1b4aa481909630373171eb5ec6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa33e0488190a135166bb67e1118 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:06 p.m.