Triple
T35118401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Mother |
E1014103
|
entity |
| Predicate | hasAspectRelationWith |
P40643
|
FINISHED |
| Object | the Maiden |
—
|
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: the Maiden | Statement: [the Mother, hasAspectRelationWith, the Maiden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAspectRelationWith Context triple: [the Mother, hasAspectRelationWith, the Maiden]
-
A.
allyRelation
Indicates a cooperative, supportive relationship in which the entities act as allies toward shared or aligned goals.
-
B.
refersToAspect
chosen
Indicates that one entity specifically references or points to a particular aspect, feature, or component of another entity.
-
C.
hasContrastingRelationshipWith
Indicates a relationship in which two entities are opposed, divergent, or markedly different in qualities, roles, or effects.
-
D.
laterRelationWith
Indicates that one entity stands in a temporal relationship to another such that it occurs or exists at a later time than the other.
-
E.
occursInRelationTo
Indicates that an event, process, or state takes place in the context of, or with reference to, another specified entity or relationship.
- 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: May 3, 2026, 4:01 p.m.