Triple
T14768363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Neufville de Villeroy |
E347062
|
entity |
| Predicate | courtFunction |
P115711
|
FINISHED |
| Object | royal counselors |
—
|
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: royal counselors | Statement: [House of Neufville de Villeroy, courtFunction, royal counselors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courtFunction Context triple: [House of Neufville de Villeroy, courtFunction, royal counselors]
-
A.
courtCode
Indicates the specific court or judicial body associated with a legal case, proceeding, or record.
-
B.
courtConnection
Indicates a relationship where one entity is linked to another through a legal or judicial proceeding, institution, or decision.
-
C.
courts
Indicates that one entity actively seeks the favor, support, or romantic interest of another through deliberate actions or overtures.
-
D.
courtContext
Indicates the legal or judicial setting, circumstances, or framework within which a court-related action or relationship takes place.
-
E.
decisionCourt
Indicates that a particular court rendered the decision or judgment in a given legal case or proceeding.
- 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec81236f081908063bb4350b7b985 |
completed | April 14, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:30 a.m.