Triple
T37459350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neptulon |
E930878
|
entity |
| Predicate | ownerClassRestriction |
P181787
|
FINISHED |
| Object | Shaman only |
—
|
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: Shaman only | Statement: [Neptulon, ownerClassRestriction, Shaman only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownerClassRestriction Context triple: [Neptulon, ownerClassRestriction, Shaman only]
-
A.
fieldRestriction
Indicates that access to or use of a particular field, area, or domain is limited or constrained by specified rules or conditions.
-
B.
membershipRelationRestrictedTo
Indicates that a membership relationship between entities is limited or constrained to a specified subset, context, or condition.
-
C.
restrictTo
Indicates that one entity limits or confines another entity’s scope, access, or applicability to a specified subset, condition, or context.
-
D.
accessRestriction
Indicates a limitation or control placed on who or what can access a particular resource, location, or information.
-
E.
ownershipRule
chosen
Indicates a rule or constraint that governs who may own, control, or have legal rights over a given entity or resource.
- F. None of above.
Provenance (3 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:17 p.m.