Triple
T27160735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aveline de Clare |
E682652
|
entity |
| Predicate | nobleStatusAcquiredThrough |
P73948
|
FINISHED |
| Object | marriage |
—
|
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: marriage | Statement: [Aveline de Clare, nobleStatusAcquiredThrough, marriage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleStatusAcquiredThrough Context triple: [Aveline de Clare, nobleStatusAcquiredThrough, marriage]
-
A.
nobleTitleAcquiredThrough
chosen
Indicates the manner, event, or process by which a person comes to obtain or be granted a particular noble title.
-
B.
hasNobleStatus
Indicates that an entity possesses a recognized noble rank, title, or aristocratic status.
-
C.
nobleRankGrantedBy
Indicates that a particular noble rank or title was formally conferred upon someone by a specific granting authority or person.
-
D.
noblePrivilege
Indicates that an entity possesses special rights, immunities, or advantages granted by virtue of noble or aristocratic status.
-
E.
hasNoble
Indicates that one entity possesses or is associated with a noble title, status, or noble individual.
- 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_69eefacf6e788190a75a64399d9e3109 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f62509f5ec8190a6bc6ca211a0f6a1 |
completed | May 2, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 9:18 a.m.