Triple
T3443647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Braunschweig |
E72622
|
entity |
| Predicate | isScientificCenterFor |
P48844
|
FINISHED |
| Object | aeronautics |
—
|
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: aeronautics | Statement: [Braunschweig, isScientificCenterFor, aeronautics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isScientificCenterFor Context triple: [Braunschweig, isScientificCenterFor, aeronautics]
-
A.
hasScienceCenter
Indicates that an entity possesses, hosts, or includes a science center as one of its facilities or components.
-
B.
hasResearchCentersIn
Indicates that an entity maintains or operates research centers located within a specified place or region.
-
C.
isAcademicCenter
Indicates that an entity functions as an academic center, typically serving as a hub for education, research, or scholarly activities within an institution.
-
D.
researchCenter
Indicates that one entity functions as a research center associated with, operated by, or focused on the other entity.
-
E.
hasResearchCenters
Indicates that an entity possesses, hosts, or is associated with one or more research centers.
- 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_69ad85b05c848190b7a28ceec2bd7b74 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adba2a605c8190a0eafdf6f25b1e38 |
completed | March 8, 2026, 6:04 p.m. |
| PD | Predicate disambiguation | batch_69adae0255b48190a9069f7871c7a012 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb1ecb02881908394f197e31431b4 |
completed | March 8, 2026, 5:29 p.m. |
Created at: March 8, 2026, 3:16 p.m.