Triple
T9399527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daniel Assange |
E226431
|
entity |
| Predicate | hasMadePublicStatementsAbout |
P68313
|
FINISHED |
| Object | Julian Assange’s legal situation |
—
|
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: Julian Assange’s legal situation | Statement: [Daniel Assange, hasMadePublicStatementsAbout, Julian Assange’s legal situation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMadePublicStatementsAbout Context triple: [Daniel Assange, hasMadePublicStatementsAbout, Julian Assange’s legal situation]
-
A.
publicStatements
chosen
Indicates that one entity makes official or public verbal or written declarations about another entity or topic.
-
B.
hasSpokenAbout
Indicates that one entity has verbally expressed, discussed, or mentioned another entity or topic.
-
C.
hasNotableClaim
Indicates that an entity is associated with a significant, widely recognized statement, assertion, or claim.
-
D.
hasBeenSubjectOf
Indicates that an entity has previously been the focus or target of a particular action, process, or investigation.
-
E.
madePublicConfessionAt
Indicates that an entity openly admitted or confessed something in a public setting at a specific time or place.
- 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_69ca843170f88190800a8ab2b5fc568e |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd51556fc08190b8ff8190a1485a3a |
completed | April 1, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69cca545b2448190a4297312e39c21ac |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:46 p.m.