Triple
T11859991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Squire |
E282133
|
entity |
| Predicate | romanticStatus |
P82370
|
FINISHED |
| Object | in love |
—
|
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: in love | Statement: [Squire, romanticStatus, in love]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanticStatus Context triple: [Squire, romanticStatus, in love]
-
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.
companionshipStatus
Indicates the current state or condition of a relationship of companionship between two or more entities.
-
C.
marital status
Indicates the legal or social state of a person’s marriage-related relationship, such as being single, married, divorced, or widowed.
-
D.
neverMarried
Indicates that the subject has not been legally married to any partner at any time up to the present.
-
E.
spouseStatus
Indicates the marital relationship status between two individuals, such as whether they are currently spouses, formerly spouses, or not married to each other.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a69a099c8190a674db64c50eca5a |
completed | April 10, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69d8a2573dbc8190ab432e8e28fde6cc |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.