Triple
T1089307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of chivalry |
E24124
|
entity |
| Predicate | hasTypicalFounder |
P23351
|
FINISHED |
| Object | Monarch |
—
|
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: Monarch | Statement: [Order of chivalry, hasTypicalFounder, Monarch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalFounder Context triple: [Order of chivalry, hasTypicalFounder, Monarch]
-
A.
founder
Indicates that an entity established, created, or started another entity such as an organization, institution, or company.
-
B.
foundingAncestor
Indicates that one entity is the original progenitor or earliest known ancestor from whom another entity or lineage descends.
-
C.
hasFounderOfDeveloper
Indicates that an entity has as its founder a specific developer who established or created it.
-
D.
foundingMember
Indicates that an entity is one of the original creators or initial participants involved in establishing another entity, such as an organization, group, or project.
-
E.
foundedWith
Indicates that an entity was established or created together with another entity, typically as co-founders or jointly initiated partners.
- 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_69a49404428c819092dcc9632f5f7b8b |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b97f216881909e9b8943ce2078e4 |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b741b0cc8190be001a16a81f6d9e |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b7bd3d50819091e6f1d2ffe4c7ee |
completed | March 1, 2026, 10:03 p.m. |
Created at: March 1, 2026, 7:42 p.m.