Triple
T4536816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George (magazine) |
E107425
|
entity |
| Predicate | coverFeature |
P997
|
FINISHED |
| Object | politicians |
—
|
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: politicians | Statement: [George (magazine), coverFeature, politicians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coverFeature Context triple: [George (magazine), coverFeature, politicians]
-
A.
cover
Indicates that one entity extends over, conceals, protects, or provides a surface or layer for another entity.
-
B.
coverLocation
Indicates that one entity serves as a covering or protective layer positioned at or over a specific location of another entity.
-
C.
notableCover
Indicates that one entity is a particularly well-known or significant cover version or adaptation of another entity.
-
D.
coversSection
Indicates that one entity includes, addresses, or provides content for a particular section of another entity.
-
E.
featuredOn
chosen
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_69bd43f922788190b7edfa294e39b178 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57b78b8481909d79131723d4be22 |
completed | March 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69bd521edd00819099dfccaa65dddd61 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:04 p.m.