Triple
T19138205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rachel, Monique |
E468485
|
entity |
| Predicate | examinesRelationship |
P63064
|
FINISHED |
| Object | artist and 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: artist and mother | Statement: [Rachel, Monique, examinesRelationship, artist and mother]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: examinesRelationship Context triple: [Rachel, Monique, examinesRelationship, artist and mother]
-
A.
exploresRelationship
chosen
Indicates that one entity actively investigates, examines, or probes the nature, dynamics, or implications of its relationship with another entity.
-
B.
showsRelationshipWith
Indicates that one entity visually or explicitly presents or demonstrates its connection or association with another entity.
-
C.
trackRelationship
Indicates a connection in which one entity monitors, follows, or keeps a record of another entity’s state, behavior, or changes over time.
-
D.
subjectRelation
Indicates that one entity stands in a specified relational role or connection to another entity.
-
E.
relationshipTestedBy
Indicates that a relationship between entities has been examined or evaluated by a specified agent, method, or test.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3ee8b988190914ef21ca1b890c6 |
completed | April 20, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.