Triple
T34138607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James McMillan Jr. |
E875639
|
entity |
| Predicate | lifeTrajectory |
P146005
|
FINISHED |
| Object | involved in street crime |
—
|
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: involved in street crime | Statement: [James McMillan Jr., lifeTrajectory, involved in street crime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifeTrajectory Context triple: [James McMillan Jr., lifeTrajectory, involved in street crime]
-
A.
lifeProgression
Indicates the sequence or advancement of an entity through different stages or phases of its life or development.
-
B.
lifeChoice
Indicates a decision or preference that significantly shapes an individual's overall way of living or long-term life direction.
-
C.
lifeShapedBy
Indicates that one entity’s life, development, or overall trajectory is significantly influenced, molded, or determined by another entity or factor.
-
D.
lifeCycle
Indicates the sequence of stages or phases an entity passes through from its beginning, through development and use, to its end or termination.
-
E.
lifeSituation
chosen
Indicates the general circumstances, conditions, or context in which an entity’s life currently exists or unfolds.
- 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_69f349aaeef08190a20e72a3fdeb7052 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:53 a.m.