Triple
T27734184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CollectionBase |
E697493
|
entity |
| Predicate | hasProtectedProperty |
P196416
|
FINISHED |
| Object | InnerList |
—
|
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: InnerList | Statement: [CollectionBase, hasProtectedProperty, InnerList]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtectedProperty Context triple: [CollectionBase, hasProtectedProperty, InnerList]
-
A.
isProtectedFrom
Indicates that one entity is safeguarded or shielded against harm, damage, or adverse effects caused by another entity or factor.
-
B.
hasProtectedStructure
Indicates that an entity possesses or is associated with a structure that is designated as protected (e.g., legally, environmentally, or culturally safeguarded).
-
C.
isProtectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
D.
isProtectedFor
Indicates that one entity is safeguarded or preserved specifically for the benefit, use, or rights of another entity.
-
E.
isProtectedName
Indicates that a given name is reserved or restricted from general use, typically to prevent conflicts, misuse, or unauthorized modification.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
| PDg | Predicate description generation | batch_69fe349739cc8190a21c408208312e6c |
completed | May 8, 2026, 7:08 p.m. |
Created at: April 27, 2026, 3:12 p.m.