Triple
T35013620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Pact |
E1009995
|
entity |
| Predicate | legalStatusAmongBosmer |
P200326
|
FINISHED |
| Object | binding religious law |
—
|
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: binding religious law | Statement: [Green Pact, legalStatusAmongBosmer, binding religious law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusAmongBosmer Context triple: [Green Pact, legalStatusAmongBosmer, binding religious law]
-
A.
legalStatusInEmpire
Indicates the formal legal standing or classification an entity holds within a particular empire’s legal and administrative system.
-
B.
legalStatusOnVulcan
Indicates the legal standing or classification an entity holds under Vulcan’s laws or legal system.
-
C.
legalStatusInUniverse
Indicates the formal legal standing or classification an entity holds within a specified fictional or conceptual universe.
-
D.
politicalStatusInLore
Indicates the character or entity’s political role, rank, or standing within the fictional world’s established lore.
-
E.
legalStatusUnderBritish
Indicates the legal status or classification an entity holds under British law or the British legal system.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff80d9a1d88190a95b1488acd6e2e5 |
completed | May 9, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69ff802ae2dc819093a3cda42b63dcbd |
completed | May 9, 2026, 6:42 p.m. |
| PDg | Predicate description generation | batch_69ff80d8ff208190b9e95d077fd99f78 |
completed | May 9, 2026, 6:45 p.m. |
Created at: May 3, 2026, 4:01 p.m.