Triple
T34894846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EUROGENDFOR |
E1006401
|
entity |
| Predicate | foundingTreatyLocation |
P35565
|
FINISHED |
| Object | Velsen |
—
|
NE NERFINISHED |
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: Velsen | Statement: [EUROGENDFOR, foundingTreatyLocation, Velsen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundingTreatyLocation Context triple: [EUROGENDFOR, foundingTreatyLocation, Velsen]
-
A.
treatySignedPlace
Indicates the location where a treaty was formally signed or concluded.
-
B.
billOfRightsLocation
Indicates the physical or archival location where a particular Bill of Rights document is kept or stored.
-
C.
foundingTreatySignedAt
chosen
Indicates that the founding treaty establishing an entity was formally signed at a specific location.
-
D.
declarationOfIndependenceLocation
Indicates the place where a declaration of independence was formally issued or adopted.
-
E.
headquartersLocationEstablishedByTreaty
Indicates that an entity’s headquarters location was determined or established as a result of a formal treaty or international agreement.
- 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_69f76dbfe5788190ad8b64f241f470c8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fedfd913f48190bdcd450980868d9a |
completed | May 9, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fedf58c6e88190821a7156054c9086 |
completed | May 9, 2026, 7:16 a.m. |
Created at: May 3, 2026, 4 p.m.