Triple
T31790424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Estrées |
E811447
|
entity |
| Predicate | sourceOfInfluence |
P31348
|
FINISHED |
| Object | royal favor |
—
|
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: royal favor | Statement: [House of Estrées, sourceOfInfluence, royal favor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceOfInfluence Context triple: [House of Estrées, sourceOfInfluence, royal favor]
-
A.
influenceOf
Indicates that one entity affects, shapes, or alters the state, behavior, or properties of another entity.
-
B.
influencedIn
Indicates that one entity had an effect on or shaped another entity within a specific context, domain, or setting.
-
C.
typeOfInfluence
chosen
Indicates the specific nature or category of influence that one entity exerts on another.
-
D.
influentialFrom
Indicates that one entity has exerted influence on another, contributing to or shaping the latter’s ideas, behavior, or development.
-
E.
wereInfluencedBy
Indicates that one entity’s ideas, actions, or characteristics were shaped or affected by another entity.
- 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 30, 2026, 11:39 p.m.