Triple
T26573172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parker immunity |
E666879
|
entity |
| Predicate | shields |
P113180
|
FINISHED |
| Object | municipalities under certain conditions |
—
|
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: municipalities under certain conditions | Statement: [Parker immunity, shields, municipalities under certain conditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shields Context triple: [Parker immunity, shields, municipalities under certain conditions]
-
A.
shieldType
Indicates the specific kind or category of shield associated with an entity or interaction.
-
B.
ShieldsSide
Indicates that one entity is positioned or aligned on a particular side of another entity’s shield.
-
C.
shieldQuarter
Indicates that one entity is depicted as a quarter (one-fourth) section of a shield in relation to another entity.
-
D.
traditionalShield
Indicates that an entity functions as or possesses a shield that is made or used according to traditional or culturally established practices.
-
E.
shieldMeaning
chosen
Indicates that one entity serves to protect, guard, or defend another entity from harm, danger, or adverse effects.
- 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_69ee9cfa21c081909e4e36e087debfc6 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 1:59 a.m.