Triple
T3022743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frog |
E82500
|
entity |
| Predicate | appliesToProductType |
P44687
|
FINISHED |
| Object | personal computer |
—
|
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: personal computer | Statement: [Frog, appliesToProductType, personal computer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToProductType Context triple: [Frog, appliesToProductType, personal computer]
-
A.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
B.
appliesToPropertyType
Indicates that something (such as a rule, constraint, or operation) is relevant to or valid for a specific type of property.
-
C.
appliesToFeature
Indicates that something (such as a rule, constraint, or configuration) is relevant to, or governs, a specific feature.
-
D.
appliesPrimarilyTo
Indicates that a property, rule, or characteristic is mainly relevant or intended for a particular entity or group, more than for others.
-
E.
supportsProduct
Indicates that one entity provides assistance, compatibility, or necessary resources for the operation, use, or maintenance of a specified product.
- 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_69ad8b1fb34081908c1b873e2b7273e1 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a963034819093d96566e9b0cea9 |
completed | March 8, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69ad961c430c8190ac48f2e3c7e7c649 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f6af3881909f4547967384114c |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 3 p.m.