Triple
T33818723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sultan of Agrabah |
E866765
|
entity |
| Predicate | lawChanged |
P30689
|
FINISHED |
| Object | A princess must marry a prince |
—
|
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: A princess must marry a prince | Statement: [Sultan of Agrabah, lawChanged, A princess must marry a prince]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lawChanged Context triple: [Sultan of Agrabah, lawChanged, A princess must marry a prince]
-
A.
lawIntroduced
Indicates that a specific law or piece of legislation has been formally proposed or brought forward for consideration within a legislative or governing body.
-
B.
legalAmendment
chosen
Indicates a formal change or modification made to an existing law, regulation, or legal document.
-
C.
hasLegalChange
Indicates that an entity has undergone or is associated with a modification in its legal status, rights, obligations, or regulatory conditions.
-
D.
legalReformer
Indicates that an entity works to change, improve, or modernize laws or legal systems.
-
E.
proposedLaw
Indicates that an entity has formally put forward a law or legislative measure for consideration or approval.
- 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fff809b881909c0c303f693eb3bc |
completed | May 3, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:46 a.m.