Triple
T33443318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solopaca |
E856422
|
entity |
| Predicate | hasDOCRecognition |
P142847
|
FINISHED |
| Object | Solopaca DOC |
—
|
NE NERFINISHED |
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: Solopaca DOC | Statement: [Solopaca, hasDOCRecognition, Solopaca DOC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDOCRecognition Context triple: [Solopaca, hasDOCRecognition, Solopaca DOC]
-
A.
recognizesDocument
Indicates that one entity acknowledges the validity or authenticity of a document associated with another entity.
-
B.
hasDOC
chosen
Indicates that one entity is associated with, linked to, or possesses a specific document or documentation.
-
C.
hasProcessOfRecognition
Indicates that one entity is involved in or characterized by a process of recognizing, identifying, or acknowledging another entity or condition.
-
D.
hasOfficialDocument
Indicates that an entity possesses or is associated with a formal, authorized document issued by a recognized authority.
-
E.
hasRecognitionList
Indicates that an entity is associated with a specific list detailing recognitions, awards, or honors it has received.
- 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_69f34971b75881908be360bb041f003c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: May 1, 2026, 1:37 a.m.