Triple
T15378685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ems |
E367740
|
entity |
| Predicate | wasPopularWith |
P729
|
FINISHED |
| Object | European aristocracy |
—
|
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: European aristocracy | Statement: [Ems, wasPopularWith, European aristocracy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasPopularWith Context triple: [Ems, wasPopularWith, European aristocracy]
-
A.
isPopularWith
chosen
Indicates that one entity is well-liked, favored, or widely accepted by another entity or group.
-
B.
isPopularAs
Indicates that an entity is widely liked, well-known, or favored in a particular role, context, or capacity.
-
C.
hasEnduringPopularityOn
Indicates that something continues to be widely liked, used, or appreciated on a particular platform, medium, or context over an extended period of time.
-
D.
hasPopularityInfluencedBy
Indicates that the popularity level of one entity is affected or shaped by another specified factor or entity.
-
E.
isPopularAt
Indicates that an entity enjoys a high level of recognition, approval, or favor within a specified place, context, or time.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e6044488190b0499db109f7f821 |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.