Triple
T36312790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | /biz/ |
E894105
|
entity |
| Predicate | hasPostFormat |
P200309
|
FINISHED |
| Object | threaded discussions |
—
|
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: threaded discussions | Statement: [/biz/, hasPostFormat, threaded discussions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPostFormat Context triple: [/biz/, hasPostFormat, threaded discussions]
-
A.
hasShowFormat
Indicates that something (such as a show or program) is associated with or presented in a particular format or style.
-
B.
hasProductionFormat
Indicates that an entity is associated with, or presented in, a particular production or media format.
-
C.
hasFormatChanges
Indicates that an entity has undergone modifications to its structure, layout, or presentation format compared to a previous or reference version.
-
D.
hasPostcodeFormat
Indicates that a location or address follows a specific postal code pattern or structure defined by a given standard.
-
E.
hasSecondaryFormat
Indicates that an entity is associated with an additional, alternative, or supplementary format beyond its primary format.
- F. None of above. chosen
Provenance (4 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_69f76e4c1b248190b10667d0213537fe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff7fc835f08190afd1f8129b7a62a2 |
completed | May 9, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69ff7f2e99ac8190ba372a1358a05a30 |
completed | May 9, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69ff7fc715208190a8e4e2cc5aa72d2c |
completed | May 9, 2026, 6:41 p.m. |
Created at: May 3, 2026, 4:09 p.m.