Triple
T33635538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julius Butler |
E861680
|
entity |
| Predicate | allegedlyBeganInforming |
P48572
|
FINISHED |
| Object | late 1960s |
—
|
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: late 1960s | Statement: [Julius Butler, allegedlyBeganInforming, late 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedlyBeganInforming Context triple: [Julius Butler, allegedlyBeganInforming, late 1960s]
-
A.
secretlyInformed
Indicates that one entity provided information to another in a concealed or confidential manner, without the knowledge of others.
-
B.
allegedStartEvent
chosen
Indicates that an entity is claimed or reported (but not confirmed) to be the starting point or initiation of a particular event or process.
-
C.
usedInforms
Indicates that one entity utilizes information from another entity to guide or shape its own actions, decisions, or outputs.
-
D.
hasAllegedDate
Indicates that an entity is associated with a date that is claimed or reported, but not confirmed as certain.
-
E.
claimedDuring
Indicates that an assertion or claim was made within a specific time period or event interval.
- 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_69f34981c54c81909b33c3fa2208a52d |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 1, 2026, 1:42 a.m.