Triple
T3744829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Go To Statement Considered Harmful |
E79784
|
entity |
| Predicate | coinedOrPopularizedPhrase |
P118
|
FINISHED |
| Object | Considered Harmful |
—
|
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: Considered Harmful | Statement: [Go To Statement Considered Harmful, coinedOrPopularizedPhrase, Considered Harmful]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coinedOrPopularizedPhrase Context triple: [Go To Statement Considered Harmful, coinedOrPopularizedPhrase, Considered Harmful]
-
A.
coinedTerm
chosen
Indicates that an entity originated and introduced a particular term or expression into use.
-
B.
popularizedBy
Indicates that something became widely known, accepted, or fashionable as a result of the influence or actions of a particular agent.
-
C.
popularizedIn
Indicates that something became widely known, accepted, or fashionable within a particular place, time period, or context.
-
D.
ideologyCoined
Indicates that one entity originated, formulated, or first introduced a particular ideology.
-
E.
usedPhrase
Indicates that one entity employed or expressed a particular phrase in speech, writing, or another form of communication.
- 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_69ad8b115610819095b02007da5ca3cb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb58c9048190a055d1f4a7e6b699 |
completed | March 8, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69adc04adebc819088d7f36d0ac343a6 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.