Triple
T33513125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Dactyloscopy system |
E858298
|
entity |
| Predicate | centralUnitLocation |
P18768
|
FINISHED |
| Object | Strasbourg |
—
|
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: Strasbourg | Statement: [European Dactyloscopy system, centralUnitLocation, Strasbourg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralUnitLocation Context triple: [European Dactyloscopy system, centralUnitLocation, Strasbourg]
-
A.
centralLocation
chosen
Indicates that one entity serves as the primary or central place associated with another entity.
-
B.
coordinationUnitLocatedIn
Indicates that a coordination unit is situated or based within a specified location or administrative area.
-
C.
centerType
Indicates the classification or category of a center (e.g., type of facility, institution, or hub) associated with an entity.
-
D.
adminCenterLocatedOn
Indicates that the administrative center of an entity is situated on or within a specified geographic or physical feature.
-
E.
platformLocation
Indicates the spatial position or placement of a platform relative to a reference point or environment.
- 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: May 1, 2026, 1:39 a.m.