Triple
T17641013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Achille Murat (by marriage) |
E429224
|
entity |
| Predicate | hasTitleOrStatus |
P12717
|
FINISHED |
| Object | noble by 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: noble by marriage | Statement: [Achille Murat (by marriage), hasTitleOrStatus, noble by marriage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleOrStatus Context triple: [Achille Murat (by marriage), hasTitleOrStatus, noble by marriage]
-
A.
hasWorkingTitleStatus
Indicates that an entity currently holds the status of having a provisional or working title rather than a finalized official title.
-
B.
hasTitleOrDescription
Indicates that an entity is associated with either a title, a description, or both.
-
C.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
D.
hasTitleOver
Indicates that one entity holds a formal title, rank, or designation in relation to another entity.
-
E.
hasStatusLabel
chosen
Indicates that an entity is associated with a specific status expressed as a human-readable label.
- 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_69d889e2c2608190b762e76d9b2262f1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46de50bf481909e938613b38f0202 |
completed | April 19, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69e3cddc87188190ac2f049b86038676 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 6:02 a.m.