Triple
T29199168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arms of the Montagu family, Earls of Sandwich |
E740219
|
entity |
| Predicate | pelletPosition |
P166421
|
FINISHED |
| Object | two in chief and one in base |
—
|
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: two in chief and one in base | Statement: [Arms of the Montagu family, Earls of Sandwich, pelletPosition, two in chief and one in base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pelletPosition Context triple: [Arms of the Montagu family, Earls of Sandwich, pelletPosition, two in chief and one in base]
-
A.
plateLocation
Indicates the spatial position or placement of a plate relative to a reference location or object.
-
B.
positionInChamber
Indicates the specific location or role an entity holds within a particular chamber or assembly.
-
C.
positionOnPillar
Indicates that one entity is located on top of or supported by a pillar.
-
D.
opusPosition
Indicates the position or number assigned to a work within a creator’s catalog or opus sequence.
-
E.
positionObtainedBy
Indicates that a particular position or role is acquired, achieved, or secured through a specified action, process, or agent.
- F. None of above. chosen
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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f663c3f12c8190b9ff4bb24bff9391 |
completed | May 2, 2026, 8:51 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65fb2ead08190b06677d4d6ea1ea8 |
completed | May 2, 2026, 8:33 p.m. |
Created at: April 28, 2026, 12:05 p.m.