Triple
T3140795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French royal court |
E65638
|
entity |
| Predicate | endedAsTraditionalInstitution |
P45609
|
FINISHED |
| Object | late 18th 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: late 18th century | Statement: [French royal court, endedAsTraditionalInstitution, late 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endedAsTraditionalInstitution Context triple: [French royal court, endedAsTraditionalInstitution, late 18th century]
-
A.
traditionalInstitution
Indicates that an entity is a long-established, customary organization or system that embodies and maintains traditional practices or norms.
-
B.
establishedInstitution
Indicates that an entity founded, created, or formally set up an institution or organization.
-
C.
hasFormerInstitution
Indicates that an entity was previously affiliated with, employed by, or enrolled in a particular institution in the past.
-
D.
recognizedAsInstitutionBy
Indicates that an entity is acknowledged or accepted as an institution by a specified recognizing party.
-
E.
servesInstitution
Indicates that one entity provides services or functions in support of a particular institution.
- 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_69ad8582f564819088c27e1f96153938 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada57895dc8190bd3d4ef9391973dc |
completed | March 8, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69ad9df840088190a26a1516f4c1f056 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f7c21c819087e9992f5fe30a37 |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:05 p.m.