Triple
T27979733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The In Campaign |
E706585
|
entity |
| Predicate | isOfficialDesignation |
P162652
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The In Campaign, isOfficialDesignation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOfficialDesignation Context triple: [The In Campaign, isOfficialDesignation, true]
-
A.
hasDesignation
Indicates that an entity holds or is assigned a specific title, label, or formal designation.
-
B.
isAbstractDesignation
Indicates that one entity serves as a non-physical, conceptual, or symbolic label or designation for another entity.
-
C.
isDesignatedAccordingTo
chosen
Indicates that an entity has a particular status, role, or classification as formally specified by a given authority, standard, or designation scheme.
-
D.
isTemporaryDesignation
Indicates that a given designation or label is intended to be used only for a limited time and is not the entity’s permanent or final designation.
-
E.
hasDesignationBy
Indicates that one entity has been formally assigned or labeled with a specific designation by another entity.
- 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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63b6802d081908721f6bb9c0d8180 |
completed | May 2, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:43 p.m.