Triple
T14144074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gendarmes de la Garde |
E350497
|
entity |
| Predicate | socialStatusOfMembers |
P38813
|
FINISHED |
| Object | high nobility |
—
|
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: high nobility | Statement: [Gendarmes de la Garde, socialStatusOfMembers, high nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialStatusOfMembers Context triple: [Gendarmes de la Garde, socialStatusOfMembers, high nobility]
-
A.
legalStatusOfMembers
Indicates the legal standing, rights, and obligations that apply to the members within a particular group or organization.
-
B.
collectivityStatus
Indicates the state or condition of being part of a collective group versus being individual or separate.
-
C.
associatedPeopleStatus
Indicates the role, condition, or standing of people who are connected or linked to a given entity or event.
-
D.
collectiveStatus
Indicates the overall state or condition shared by a group of entities considered together as a collective.
-
E.
statusInCommunity
chosen
Indicates the social standing, role, or level of acceptance an entity holds within a particular community.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61214de081909a5186ff11336f97 |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:53 a.m.