Triple
T24057551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maggie Hardin |
E595848
|
entity |
| Predicate | triesToOrchestrate |
P67492
|
FINISHED |
| Object | her own love life |
—
|
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: her own love life | Statement: [Maggie Hardin, triesToOrchestrate, her own love life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: triesToOrchestrate Context triple: [Maggie Hardin, triesToOrchestrate, her own love life]
-
A.
helpsOrchestrate
chosen
Indicates involvement in coordinating, organizing, or managing the execution of an activity or process, often in collaboration with others.
-
B.
usesOrchestration
Indicates that one entity employs orchestration mechanisms or tools to coordinate, manage, or automate the behavior and interactions of other entities or processes.
-
C.
orchestratedFor
Indicates that one entity planned, coordinated, or arranged something specifically on behalf of or for the benefit of another entity.
-
D.
hasOrchestration
Indicates that one entity coordinates, manages, or sequences the actions or interactions of another entity or set of entities.
-
E.
orchestrator
Indicates coordinating and directing the actions or interactions of multiple entities to achieve a unified outcome.
- 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_69e288c184b081909f1f1751fb8e299a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1da50d6108190a36bffaa475c8b93 |
completed | April 29, 2026, 10:15 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:35 p.m.