Triple
T1254557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vetus Ordo |
E26956
|
entity |
| Predicate | normativeFormUntil |
P25859
|
FINISHED |
| Object | mid‑20th century |
—
|
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: mid‑20th century | Statement: [Vetus Ordo, normativeFormUntil, mid‑20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: normativeFormUntil Context triple: [Vetus Ordo, normativeFormUntil, mid‑20th century]
-
A.
normativeFor
Indicates that something establishes, prescribes, or encodes the norms, standards, or rules that should govern another thing’s behavior or state.
-
B.
formalizedAt
Indicates the point in time or event at which something is officially established, documented, or given formal status.
-
C.
isFormalizedBy
Indicates that something is given a defined, structured, or official form through a specific method, process, or representation.
-
D.
formalizationDate
Indicates the date on which something is officially established, formalized, or brought into an official or legally recognized form.
-
E.
hasNorm
Indicates that an entity is associated with, governed by, or characterized through a particular norm, rule, or standard.
- 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_69a49487a9c48190ba9b05348fd1b53f |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bfa5a4cc819093ed686619b572d8 |
completed | March 1, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6c977c8190a2bf3e8b67a59beb |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bc49693c8190978ec63a5171d342 |
completed | March 1, 2026, 10:23 p.m. |
Created at: March 1, 2026, 7:47 p.m.