Triple
T20567123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fajia |
E504993
|
entity |
| Predicate | mainTenet |
P140591
|
FINISHED |
| Object | emphasis on strict laws |
—
|
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: emphasis on strict laws | Statement: [Fajia, mainTenet, emphasis on strict laws]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainTenet Context triple: [Fajia, mainTenet, emphasis on strict laws]
-
A.
principle10
Indicates that one entity adheres to, embodies, or is governed by a specific tenth principle within a defined set of rules or guidelines.
-
B.
mainRite
Indicates that one ritual, ceremony, or rite is the primary or central rite associated with a given context, entity, or event.
-
C.
principle1
Indicates that one entity serves as a primary rule, guideline, or foundational principle governing or guiding another entity.
-
D.
mainTenant
Indicates that the subject is the primary tenant responsible for a property or rental agreement, as opposed to a subtenant or secondary occupant.
-
E.
principle11
Indicates that an entity is governed or characterized by the eleventh principle within a defined ordered set of principles.
- 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_69e0b4b6587c8190aee63dc7cff244ea |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a7a33f7c8190966da03528dfe8aa |
completed | April 20, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69e59ff0116c8190a163ff28ed01430a |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a824748190bbe6192d73f3c613 |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:39 a.m.