Triple
T15556343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Meehan |
E370878
|
entity |
| Predicate | hadHistoryOf |
P37550
|
FINISHED |
| Object | restraining orders against him |
—
|
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: restraining orders against him | Statement: [John Meehan, hadHistoryOf, restraining orders against him]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadHistoryOf Context triple: [John Meehan, hadHistoryOf, restraining orders against him]
-
A.
hasHistoryOf
chosen
Indicates that an entity has a documented prior occurrence or background of a specified condition, event, or state.
-
B.
hasHistoryIn
Indicates that an entity has a past involvement, presence, or record of activity within a particular domain, context, or location.
-
C.
hasHad
Indicates that an entity previously experienced, possessed, or was involved in something at some point in the past.
-
D.
hadCondition
Indicates that an entity experienced or was diagnosed with a particular medical or health-related condition.
-
E.
hadEvent
Indicates that an entity experienced, hosted, or was associated with a specific event at some point in time.
- 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04a97dbfc8190a98cbbac5e71ba88 |
completed | April 16, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69deda7e6e748190b29ccce23298afef |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:09 a.m.