Triple
T34835972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radulph |
E1004197
|
entity |
| Predicate | wasCommonAmong |
P140874
|
FINISHED |
| Object | European nobles |
—
|
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 nobles | Statement: [Radulph, wasCommonAmong, European nobles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasCommonAmong Context triple: [Radulph, wasCommonAmong, European nobles]
-
A.
hadCommon
chosen
Indicates that two or more entities shared the same attribute, experience, or element in common.
-
B.
wasAmong
Indicates that an entity belonged to, was included in, or was part of a particular group, set, or collection.
-
C.
moreCommonAs
Indicates that one thing occurs or is observed more frequently in a specified role, form, or context than in another.
-
D.
wereOften
Indicates that the related entities frequently or repeatedly exhibited the specified state, behavior, or relationship in the past.
-
E.
moreCommonIn
Indicates that something occurs with greater frequency or prevalence in one group, context, or location than in another.
- 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_69f76db7d1b4819093bd4912d80d845d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.