Triple
T37476856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A-23 |
E931303
|
entity |
| Predicate | isPrintedOnTechnicalDocumentation |
P195259
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [A-23, isPrintedOnTechnicalDocumentation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrintedOnTechnicalDocumentation Context triple: [A-23, isPrintedOnTechnicalDocumentation, true]
-
A.
isTypicallyPrinted
Indicates that something is commonly or usually produced in printed form rather than in another medium.
-
B.
isPrinted
Indicates that a physical copy of an item has been produced using a printing process.
-
C.
isTechnical
Indicates that an entity possesses specialized technical knowledge, skills, or characteristics related to technology, engineering, or applied sciences.
-
D.
isPrintedAs
Indicates that one entity appears in physical or visual form as another entity, such as a specific representation, format, or layout used when it is printed or displayed.
-
E.
hasPrintFeature
Indicates that an entity possesses a specific printing-related characteristic or capability.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
| PDg | Predicate description generation | batch_69fdb3172b808190b590d7c5be31ebb7 |
completed | May 8, 2026, 9:55 a.m. |
Created at: May 3, 2026, 4:17 p.m.