Triple
T10158590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Usenet |
E233830
|
entity |
| Predicate | typicalMessageFormat |
P59120
|
FINISHED |
| Object | plain text |
—
|
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: plain text | Statement: [Usenet, typicalMessageFormat, plain text]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMessageFormat Context triple: [Usenet, typicalMessageFormat, plain text]
-
A.
typicalUsageFormat
chosen
Indicates the usual or standard way in which something is expressed, presented, or formatted in practice.
-
B.
typicalForm
Indicates that one entity represents the standard, characteristic, or most common form or shape in which another entity typically appears or is realized.
-
C.
typicalAnnouncementFormat
Indicates that an announcement customarily follows a particular structure, style, or format.
-
D.
intendedMessage
Indicates that one entity is the message or content that another entity aims or plans to communicate.
-
E.
formatMayChange
Indicates that the format or structure of something is subject to modification and may not remain consistent over 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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec56d944819081bc6ea36c905ba2 |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba795808190acc9124c98c6e40f |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:09 p.m.