Triple
T13609768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rachel Green |
E325157
|
entity |
| Predicate | weddingStatusInPilot |
P110404
|
FINISHED |
| Object | runaway bride |
—
|
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: runaway bride | Statement: [Rachel Green, weddingStatusInPilot, runaway bride]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weddingStatusInPilot Context triple: [Rachel Green, weddingStatusInPilot, runaway bride]
-
A.
nuptialFlightTrigger
Indicates the condition or event that initiates or triggers a nuptial flight between mating individuals.
-
B.
spouseStatusAtMarriage
Indicates the marital status each partner held at the time their marriage to one another was formed.
-
C.
marriageLegalStatus
Indicates the legal status of a marriage relationship between entities, such as whether it is valid, invalid, pending, or dissolved under applicable law.
-
D.
hasMaritalStatusAtEnd
Indicates that an entity possesses a specific marital status at the end of a given period, event, or reference time.
-
E.
marriageType
Indicates the specific legal or social category of a marriage relationship that exists between two spouses.
- 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_69d8076aae28819092cf636190ee5529 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae1b3ee481909bd43ded6227a3e5 |
completed | April 12, 2026, 2:37 p.m. |
| PDg | Predicate description generation | batch_69dbbb8c77dc8190b7bd803b5e168d23 |
completed | April 12, 2026, 3:34 p.m. |
Created at: April 9, 2026, 9:50 p.m.