Triple
T9429729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jenna Maroney |
E227340
|
entity |
| Predicate | hasFlaw |
P45135
|
FINISHED |
| Object | egoism |
—
|
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: egoism | Statement: [Jenna Maroney, hasFlaw, egoism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFlaw Context triple: [Jenna Maroney, hasFlaw, egoism]
-
A.
hasCrack
Indicates that one entity possesses or exhibits a crack, fracture, or split in its structure or surface.
-
B.
hasFlaring
Indicates that an entity exhibits or is associated with a flaring event or flaring activity.
-
C.
hasDam
Indicates that a watercourse, reservoir, or similar feature is impounded or controlled by a specific dam.
-
D.
raisesIssue
Indicates that one entity brings up, reports, or formally submits a concern, problem, or topic for attention to another entity or system.
-
E.
possibleIssue
chosen
Indicates that there is a potential or suspected problem, defect, or undesired condition associated with the referenced entity or situation, though it is not yet confirmed.
- 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_69ca8436ba308190903e470776d2d893 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd7c94719c81909d7743a57c45e07f |
completed | April 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69cca55548488190b171ae695a3212de |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:49 p.m.