Triple
T29592994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louis XIV of France |
E754217
|
entity |
| Predicate | courtPerson |
P170168
|
FINISHED |
| Object | Laura Mancini |
—
|
NE NERFINISHED |
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: Laura Mancini | Statement: [Louis XIV of France, courtPerson, Laura Mancini]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courtPerson Context triple: [Louis XIV of France, courtPerson, Laura Mancini]
-
A.
courtMember
Indicates that an individual serves as a member of a particular court or judicial body.
-
B.
courtOfficial
Indicates that an entity serves in an official capacity within a court, holding an authorized role in judicial or legal proceedings.
-
C.
courtRole
Indicates the specific capacity or position an entity holds within a court proceeding or judicial context.
-
D.
judicialHead
Indicates that one entity serves as the chief or leading judicial authority over another entity, such as a court or legal body.
-
E.
judicialRole
Indicates that one entity holds or performs a specific official function or position within the judicial system in relation to another entity or legal matter.
- F. None of above. chosen
Provenance (4 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_69f0ef836ac88190bd809dc58b5ec907 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f68b121eac81909e90416207bc1157 |
completed | May 2, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f68a160374819084d720985f800dfc |
completed | May 2, 2026, 11:34 p.m. |
Created at: April 28, 2026, 6:15 p.m.