Triple
T9538685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morges |
E230089
|
entity |
| Predicate | foundingEventYear |
P4025
|
FINISHED |
| Object | 1961 |
—
|
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: 1961 | Statement: [Morges, foundingEventYear, 1961]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundingEventYear Context triple: [Morges, foundingEventYear, 1961]
-
A.
foundedOn
Indicates that an entity was established, created, or brought into existence on a specific date or point in time.
-
B.
foundingAround
Indicates that an entity was founded at approximately, but not exactly, the specified time or within a loosely defined surrounding period.
-
C.
foundingOf
Indicates the event or relationship in which an entity is established or created, typically linking the founder(s), the founded entity, and the time or context of its creation.
-
D.
isFoundedOn
Indicates that one entity is established, created, or based upon another entity as its foundational source or principle.
-
E.
foundedAt
chosen
Indicates the time or date at which an entity (such as an organization, project, or institution) was established or created.
- 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_69ca847b1b3081908f72bc932c17cc41 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98cfead8819089a8f47ea83500a4 |
completed | April 1, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69ccd58bd21881908b860e3ee469af13 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:01 p.m.