Triple
T37032168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A-10 |
E916524
|
entity |
| Predicate | isUsedInTechnicalDocumentation |
P38828
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [A-10, isUsedInTechnicalDocumentation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedInTechnicalDocumentation Context triple: [A-10, isUsedInTechnicalDocumentation, yes]
-
A.
documentedUsing
chosen
Indicates that something is recorded, described, or specified by means of a particular document, tool, or documentation method.
-
B.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
C.
isTechnical
Indicates that an entity possesses specialized technical knowledge, skills, or characteristics related to technology, engineering, or applied sciences.
-
D.
hasLimitedDocumentation
Indicates that the subject is associated with documentation that is sparse, incomplete, or not sufficiently detailed.
-
E.
usedInLibrary
Indicates that something is utilized or applied within the context of a library, such as a software library or a physical library system.
- 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_69f76e92c7648190bcfa277f64c71a21 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.