Triple
T37470469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Covenant Sanctum |
E931138
|
entity |
| Predicate | factionRestriction |
P189407
|
FINISHED |
| Object | none |
—
|
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: none | Statement: [Covenant Sanctum, factionRestriction, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: factionRestriction Context triple: [Covenant Sanctum, factionRestriction, none]
-
A.
politicalRestriction
Indicates that there are limitations or prohibitions imposed on an entity’s political activities, rights, or participation.
-
B.
movementRestrictions
Indicates limitations, rules, or prohibitions that constrain how, where, or when an entity is allowed to move.
-
C.
tribalRestriction
Indicates a limitation, condition, or rule that applies specifically based on tribal affiliation or tribal status.
-
D.
votingRestriction
Indicates that there is a rule or limitation affecting who can vote, how they can vote, or under what conditions voting is allowed.
-
E.
hasCitizenshipRestriction
Indicates that there is a legal or policy-based limitation on who can obtain or hold citizenship in a given context.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbbc48b75c8190bec27dd4b7de797f |
completed | May 6, 2026, 10:10 p.m. |
Created at: May 3, 2026, 4:17 p.m.