Triple
T177195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FCS |
E3597
|
entity |
| Predicate | primaryMediaCoverageLevel |
P1782
|
FINISHED |
| Object | lower than FBS |
—
|
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: lower than FBS | Statement: [FCS, primaryMediaCoverageLevel, lower than FBS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryMediaCoverageLevel Context triple: [FCS, primaryMediaCoverageLevel, lower than FBS]
-
A.
mediaCoverage
chosen
Indicates that one entity reports on, documents, or broadcasts information about another entity through news or media channels.
-
B.
primaryContent
Indicates that one entity serves as the main or most important content associated with another entity.
-
C.
primarySources
Indicates that one entity serves as an original, authoritative source of information or evidence for another entity.
-
D.
primaryAlignment
Indicates the main or most significant way in which one entity is aligned, associated, or in agreement with another entity, standard, or category.
-
E.
featuredOn
Indicates that one entity is prominently presented, highlighted, or showcased on or within another entity (such as a platform, publication, or product).
- 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_69a25374990081909766d30c79a18e0e |
completed | Feb. 28, 2026, 2:31 a.m. |
| NER | Named-entity recognition | batch_69a258fd278481908ad4498e03f38e2f |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a25669d99481908c5e82ba8641205a |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:39 a.m.