Triple
T29268375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jelebu (P126) |
E742040
|
entity |
| Predicate | isPublicLawEntity |
P167409
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Jelebu (P126), isPublicLawEntity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPublicLawEntity Context triple: [Jelebu (P126), isPublicLawEntity, true]
-
A.
usesLegalEntity
Indicates that one entity makes use of, operates through, or conducts activities via a particular legal entity (such as a company, organization, or other legally recognized body).
-
B.
isPublicLawJurisdiction
Indicates that a given entity falls under the authority or scope of public law within a specified jurisdiction.
-
C.
isPrincipalBodyOfLawFor
Indicates that one body of law serves as the main or primary legal framework governing a particular subject, domain, or context.
-
D.
hasLegalStructure
Indicates that an entity possesses a specific formal legal organization or classification under law.
-
E.
isCentralLegalServiceOf
Indicates that an entity functions as the primary or main legal service provider for another entity or organizational unit.
- 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_69f0912124d48190a046642b69407f4c |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 12:46 p.m.