Triple
T11170053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mask |
E264250
|
entity |
| Predicate | focusesOnRelationshipWith |
P31
|
FINISHED |
| Object | mother |
—
|
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: mother | Statement: [Mask, focusesOnRelationshipWith, mother]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusesOnRelationshipWith Context triple: [Mask, focusesOnRelationshipWith, mother]
-
A.
relationshipFocus
Indicates a relationship where particular attention, priority, or emphasis is placed on the connection between two or more entities.
-
B.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
-
C.
showsRelationshipWith
Indicates that one entity visually or explicitly presents or demonstrates its connection or association with another entity.
-
D.
focusesOn
chosen
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
E.
closeRelationship
Indicates a strong, intimate, or emotionally significant bond between two entities, suggesting familiarity, trust, and frequent or meaningful interaction.
- 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_69d6aa9dafac8190bd90d2c74f661aa7 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8952e248190b0751669e8c960b7 |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cf0e6e88190973694abe2990973 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.