Triple
T15987715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luke and Laura wedding |
E387738
|
entity |
| Predicate | hasCoupleType |
P15570
|
FINISHED |
| Object | supercouple |
—
|
LITERAL FINISHED |
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: supercouple | Statement: [Luke and Laura wedding, hasCoupleType, supercouple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoupleType Context triple: [Luke and Laura wedding, hasCoupleType, supercouple]
-
A.
hasMaritalRelationshipType
Indicates the specific type or nature of the marital relationship that exists between two entities.
-
B.
hasCoupling
Indicates that two entities are linked or joined together in a way that allows them to interact, transfer, or coordinate motion, energy, or information.
-
C.
hasBondType
Indicates the specific kind of bond or connection that exists between two related entities.
-
D.
hasPartnershipType
chosen
Indicates the specific kind or category of partnership relationship that exists between entities.
-
E.
hasExPartner
Indicates that one entity was formerly in a romantic or intimate partnership with another entity, but that relationship has ended.
- 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_69d86daa562c81908aacc179c0fe8fb5 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4e871c819082d7b1c1eaf5b4fe |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d9d8e881909b559a3e3ca21d24 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:54 a.m.