Triple
T37459627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malorne |
E930884
|
entity |
| Predicate | ownerRestriction |
P190539
|
FINISHED |
| Object | Druid 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: Druid only | Statement: [Malorne, ownerRestriction, Druid only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownerRestriction Context triple: [Malorne, ownerRestriction, Druid only]
-
A.
accessRestriction
Indicates a limitation or control placed on who or what can access a particular resource, location, or information.
-
B.
ownershipRule
Indicates a rule or constraint that governs who may own, control, or have legal rights over a given entity or resource.
-
C.
accessRestrictedTo
Indicates that access to a resource, location, or information is limited exclusively to a specified entity or group under defined conditions.
-
D.
ownershipRequirement
Indicates that a certain level or type of ownership must be held by an entity in order for a condition, action, or relationship to be valid or applicable.
-
E.
hasHumanUseRestriction
Indicates that there is a limitation or condition on how something may be used by humans.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcc7779d248190afdb348a95375443 |
completed | May 7, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
| PDg | Predicate description generation | batch_69fcc73264e08190b0b5917f32226fae |
completed | May 7, 2026, 5:09 p.m. |
Created at: May 3, 2026, 4:17 p.m.