Triple
T32877023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | kal-if-fee |
E840955
|
entity |
| Predicate | legalStatusOnVulcan |
P198830
|
FINISHED |
| Object | sanctioned tradition |
—
|
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: sanctioned tradition | Statement: [kal-if-fee, legalStatusOnVulcan, sanctioned tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusOnVulcan Context triple: [kal-if-fee, legalStatusOnVulcan, sanctioned tradition]
-
A.
legalStatusInUniverse
Indicates the formal legal standing or classification an entity holds within a specified fictional or conceptual universe.
-
B.
legalStatusAtIssue
Indicates that the legal status of an entity is the central subject of dispute, consideration, or determination in a legal context.
-
C.
legalStatusAtDiscovery
Indicates the legal status or condition of an entity at the specific time it was discovered or first identified.
-
D.
legalStatusClarifiedBy
Indicates that the legal status of something is defined, explained, or resolved by a specific document, decision, or authoritative act.
-
E.
legalStatusAtApproval
Indicates the legal status or classification an entity held at the time it was formally approved.
- 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_69f349436ee88190b72ee12d0f3f508e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff0d80c0dc81909fbd12285c7a45c0 |
completed | May 9, 2026, 10:33 a.m. |
| PD | Predicate disambiguation | batch_69ff0cd03e78819094895058f925fbfa |
completed | May 9, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69ff0d800ee88190835e233d9e846cdb |
completed | May 9, 2026, 10:33 a.m. |
Created at: May 1, 2026, 1:18 a.m.