Triple
T702938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gold |
E14037
|
entity |
| Predicate | partOfGroup |
P1925
|
FINISHED |
| Object | five main Allied landing beaches in Normandy |
—
|
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: five main Allied landing beaches in Normandy | Statement: [Gold, partOfGroup, five main Allied landing beaches in Normandy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfGroup Context triple: [Gold, partOfGroup, five main Allied landing beaches in Normandy]
-
A.
partOfSystem
Indicates that one entity functions as a component or subsystem within the structure or organization of another entity.
-
B.
partOfCollection
chosen
Indicates that an entity belongs to, or is included within, a larger collection or set.
-
C.
hasPartIn
Indicates that an entity participates in or plays a role within a larger event, process, or composite entity.
-
D.
belongsToGroup
Indicates that an entity is a member of, or is included within, a particular group or collection.
-
E.
coveredGroup
Indicates that one group or set is included within, or has its members protected or accounted for by, another group or arrangement.
- 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_69a493494ec48190ae6751683625a9ba |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a58d4c3c8190ad4527d14bca5e6e |
completed | March 1, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69a4a4edc33881909a978268f6dd5d82 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:36 p.m.