Triple
T38261829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 42 Zurich |
E1017947
|
entity |
| Predicate | hasTraditionalClasses |
P202216
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [42 Zurich, hasTraditionalClasses, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalClasses Context triple: [42 Zurich, hasTraditionalClasses, no]
-
A.
hasTraditionalFeatures
Indicates that something possesses characteristics or attributes commonly associated with established traditions or customary practices.
-
B.
hasTraditionalBase
Indicates that something is supported by, built upon, or derived from an established traditional foundation or practice.
-
C.
hasTraditionalResource
Indicates that an entity possesses or is associated with a resource that is considered traditional within a particular cultural, historical, or customary context.
-
D.
hasTraditionalPatternsType
Indicates that one entity is associated with a specific type or category of traditional patterns present in or applied to it.
-
E.
hasTraditionalEnvironment
Indicates that an entity is associated with or situated within a customary or historically established environment or setting.
- 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_69f76de33e4481909099fa812709bd42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0062e6bd788190a7b4f3e5befb5cbb |
completed | May 10, 2026, 10:50 a.m. |
| PD | Predicate disambiguation | batch_6a0061989d188190b4815b2de3e8676f |
completed | May 10, 2026, 10:44 a.m. |
| PDg | Predicate description generation | batch_6a0062e60b648190b59ea90cb7918b9a |
completed | May 10, 2026, 10:50 a.m. |
Created at: May 3, 2026, 4:30 p.m.