Triple
T25938908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Gayelette |
E653636
|
entity |
| Predicate | numberOfObligatoryServices |
P192748
|
FINISHED |
| Object | three |
—
|
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: three | Statement: [Queen Gayelette, numberOfObligatoryServices, three]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfObligatoryServices Context triple: [Queen Gayelette, numberOfObligatoryServices, three]
-
A.
hasEssentialServices
Indicates that one entity provides or contains the fundamental services or utilities necessary for the functioning or well-being of another entity.
-
B.
isObligatory
Indicates that an entity is required or must be performed, fulfilled, or complied with according to some rule, norm, or obligation.
-
C.
hasConstituentServicesIn
Indicates that an entity provides constituent services within a specified geographic or jurisdictional area.
-
D.
isOftenRequiredFor
Indicates that one entity is frequently needed or commonly necessary for the occurrence, use, or success of another entity or activity.
-
E.
requiredToProvide
Indicates that one entity has an obligation or duty to supply or furnish something to another entity.
- 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_69e7ab3fd2f881908837305e4ba98011 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
| PDg | Predicate description generation | batch_69fd2a2095f88190bfcbcb2973516ffc |
completed | May 8, 2026, 12:11 a.m. |
Created at: April 22, 2026, 8:40 a.m.