Triple
T24612929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fils de France |
E609168
|
entity |
| Predicate | entailsResidencePrivilege |
P50598
|
FINISHED |
| Object | right to reside at the royal court |
—
|
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: right to reside at the royal court | Statement: [Fils de France, entailsResidencePrivilege, right to reside at the royal court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entailsResidencePrivilege Context triple: [Fils de France, entailsResidencePrivilege, right to reside at the royal court]
-
A.
hasExclusiveResidence
Indicates that an entity resides in exactly one specific place and has no other concurrent residences.
-
B.
grantedResidence
chosen
Indicates that one entity has officially conferred the right to reside or live in a place or jurisdiction to another entity.
-
C.
hasResidenceFeature
Indicates that a residence possesses or is characterized by a specific feature or attribute.
-
D.
ownedResidence
Indicates that one entity has ownership of a dwelling or place of residence associated with another entity.
-
E.
isPrivateResidence
Indicates that a location functions as a privately owned dwelling not generally open or accessible to the public.
- 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_69e2c4d1140081909c58667bf68f80c3 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:31 a.m.