Triple
T31945744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orleanist (July Monarchy) |
E815646
|
entity |
| Predicate | keySupportBase |
P105983
|
FINISHED |
| Object | financial bourgeoisie |
—
|
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: financial bourgeoisie | Statement: [Orleanist (July Monarchy), keySupportBase, financial bourgeoisie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keySupportBase Context triple: [Orleanist (July Monarchy), keySupportBase, financial bourgeoisie]
-
A.
keySupportFrom
chosen
Indicates that one entity provides essential backing, endorsement, or assistance that is crucial for the success or continuation of another entity or action.
-
B.
supportsKeyboard
Indicates that one entity is compatible with or able to be operated using a keyboard as an input method.
-
C.
keyboardFeature
Indicates that one entity is a feature, characteristic, or functional attribute of a keyboard.
-
D.
keyBase
Indicates a base or primary key relationship, where one entity serves as the fundamental key reference for another.
-
E.
keyBase
Indicates that one entity serves as the primary or foundational key upon which another entity or structure is based.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b27930d881909d5bef056bf5e7e5 |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:06 a.m.