Triple
T36176830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magna Charta Observatory |
E1046595
|
entity |
| Predicate | hasMainDocument |
P60019
|
FINISHED |
| Object | Magna Charta Universitatum |
E323257
|
NE 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: Magna Charta Universitatum | Statement: [Magna Charta Observatory, hasMainDocument, Magna Charta Universitatum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainDocument Context triple: [Magna Charta Observatory, hasMainDocument, Magna Charta Universitatum]
-
A.
hasMainBody
Indicates that one entity serves as the primary physical or structural body of another entity.
-
B.
hasMainElements
Indicates that something possesses or is composed of its primary or most important constituent parts.
-
C.
hasMainSource
chosen
Indicates that one entity serves as the primary or principal source or origin for another entity.
-
D.
hasMainForm
Indicates that one entity is the primary or canonical form of another related entity.
-
E.
hasMainStructure
Indicates that one entity serves as the primary or central structural component of another entity.
- F. None of above.
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_69f76e3c1b10819081fc7a807a71cf84 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a03213d35788190bdf04e19625b4060 |
completed | May 12, 2026, 12:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a396df8b51c8190aa6e01c48625f673 |
completed | June 22, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_6a031ea131d48190ab0fecb48b8e2205 |
completed | May 12, 2026, 12:35 p.m. |
Created at: May 3, 2026, 4:08 p.m.