Triple
T38698289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British press corps in Moscow |
E950064
|
entity |
| Predicate | typicalEmployers |
P28583
|
FINISHED |
| Object | BBC |
E14486
|
NE 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: BBC | Statement: [British press corps in Moscow, typicalEmployers, BBC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEmployers Context triple: [British press corps in Moscow, typicalEmployers, BBC]
-
A.
typicalEmployer
chosen
Indicates that one entity is the kind of organization or person that commonly or usually employs the other entity.
-
B.
typicalEmployerUnit
Indicates that one entity is the standard or characteristic organizational unit that employs or is expected to employ another entity.
-
C.
typicalEmployerBrand
Indicates that an entity is the employer brand that is most commonly or characteristically associated with another entity.
-
D.
targetCompanies
Indicates that certain companies are the intended focus or recipients of a particular action, effort, or objective.
-
E.
typicalEnterprises
Indicates that an entity is a standard or representative example of enterprises within a given context or category.
- F. None of above.
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_69f76f0124408190bb39c3040734846b |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a420e0889e4819098b40228702d3148 |
completed | June 29, 2026, 6:17 a.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:33 p.m.