Triple
T29445013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massassi |
E746822
|
entity |
| Predicate | templeUse |
P167431
|
FINISHED |
| Object | Sith laboratories |
—
|
NE NERFINISHED |
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: Sith laboratories | Statement: [Massassi, templeUse, Sith laboratories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: templeUse Context triple: [Massassi, templeUse, Sith laboratories]
-
A.
templePractice
Indicates a religious or ritual activity that is performed within or in connection with a temple.
-
B.
templeAccess
Indicates that an entity has permission or the ability to enter or use a particular temple or temple-related area.
-
C.
isActiveTemple
Indicates that a temple is currently functioning and in regular religious use, rather than being abandoned, ruined, or inactive.
-
D.
templeState
Indicates that a temple is in a particular condition, status, or phase (such as operational, under construction, abandoned, or ceremonial).
-
E.
templeType
Indicates the specific category or classification of a temple in terms of its form, function, or religious/architectural style.
- 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66b203bd481908eb67bc9f7e0e5a9 |
completed | May 2, 2026, 9:22 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, 3:26 p.m.