Triple
T31579627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ghopuz |
E805786
|
entity |
| Predicate | stringStatus |
P137887
|
FINISHED |
| Object | not a string instrument |
—
|
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: not a string instrument | Statement: [ghopuz, stringStatus, not a string instrument]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stringStatus Context triple: [ghopuz, stringStatus, not a string instrument]
-
A.
statusInText
Indicates that the text explicitly states or conveys the status or condition of an entity.
-
B.
binaryStatus
chosen
Indicates that something has one of two possible states or conditions, typically representing a simple on/off or true/false status.
-
C.
textStatus
Indicates the current state or condition of a piece of text, such as its progress, validity, or processing outcome.
-
D.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
E.
structureStatus
Indicates the current condition or state of completion of a structure in relation to its intended design or function.
- 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8083a488190918c52744b210af5 |
completed | May 3, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:22 p.m.