Triple
T36172025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ann August |
E1046167
|
entity |
| Predicate | motherCharacteristic |
P38488
|
FINISHED |
| Object | ambitious |
—
|
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: ambitious | Statement: [Ann August, motherCharacteristic, ambitious]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: motherCharacteristic Context triple: [Ann August, motherCharacteristic, ambitious]
-
A.
motherType
Indicates the specific category or role of motherhood that one entity has in relation to another (e.g., biological, adoptive, step).
-
B.
motherCharacterName
Indicates that one character is the mother of another character, specifying a maternal parent-child relationship between them.
-
C.
familyCharacteristic
chosen
Indicates that a particular trait, feature, or quality is shared within or typical of members of the same family.
-
D.
motherIs
Indicates that one entity is the mother (biological or adoptive) of another entity.
-
E.
motherBasedOn
Indicates a maternal relationship where one entity is considered the mother of another based on inferred, indirect, or non-biological evidence or criteria.
- 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_69f76e396bc88190b99d221bff9be27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.