Triple
T16616223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pickering v. Board of Education |
E403701
|
entity |
| Predicate | involvesExpression |
P119932
|
FINISHED |
| Object | letter to a local newspaper |
—
|
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: letter to a local newspaper | Statement: [Pickering v. Board of Education, involvesExpression, letter to a local newspaper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesExpression Context triple: [Pickering v. Board of Education, involvesExpression, letter to a local newspaper]
-
A.
hasExpressionIn
chosen
Indicates that one entity is manifested, represented, or realized within another entity, typically as a specific form, version, or expression.
-
B.
isPartOfExpression
Indicates that something functions as a component or constituent element within a larger expression.
-
C.
hasExpression
Indicates that an entity displays or possesses a particular facial or emotional expression.
-
D.
involves
Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
-
E.
entersExpression
Indicates that one entity moves into, penetrates, or passes through another entity or defined space.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e375494260819099b6988857c52dde |
completed | April 18, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.