Triple
T30605936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montana Moore |
E779043
|
entity |
| Predicate | romanticStatusAtStart |
P82370
|
FINISHED |
| Object | single |
—
|
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: single | Statement: [Montana Moore, romanticStatusAtStart, single]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanticStatusAtStart Context triple: [Montana Moore, romanticStatusAtStart, single]
-
A.
romanticRelationshipStatus
chosen
Indicates the nature or state of a romantic relationship between entities, such as whether they are dating, committed, separated, or otherwise romantically involved.
-
B.
believedSpouseStatusAtStart
Indicates the marital status a person was believed to have at the beginning of a specified period or event.
-
C.
formerRelationshipStatus
Indicates that a relationship between entities existed in the past but no longer holds in the present.
-
D.
spouseStatusAtMarriage
Indicates the marital status each partner held at the time their marriage to one another was formed.
-
E.
lifeStatusAtStart
Indicates the life status or condition of an entity at the beginning of a specified event or time period.
- 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_69f224a21fc08190abd9d8dd9eb6bb4c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 29, 2026, 8:25 p.m.