Triple
T32469012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aunt Sarah |
E829792
|
entity |
| Predicate | installs |
P174211
|
FINISHED |
| Object | muzzle on Lady |
—
|
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: muzzle on Lady | Statement: [Aunt Sarah, installs, muzzle on Lady]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: installs Context triple: [Aunt Sarah, installs, muzzle on Lady]
-
A.
intendedInstallation
Indicates that one entity is meant or planned to be installed in, on, or as part of another entity or environment.
-
B.
installedFor
Indicates that something has been set up or put in place to be used by or on behalf of a particular entity.
-
C.
installationFeature
Indicates that one entity serves as a feature, component, or functional element of another entity’s installation.
-
D.
includesInstallation
Indicates that one entity comes with or provides the installation of another entity as part of its offering or package.
-
E.
supportsInstallation
Indicates that one entity is capable of enabling, handling, or being compatible with the installation of another entity.
- 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_69f3491ee87c81908cbf5890079c2af6 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c35400148190952f711f098ae7a3 |
completed | May 3, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_69f6ba700a708190ab6db62791e43774 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bbbe23d48190b2aa662d69b41900 |
completed | May 3, 2026, 3:06 a.m. |
Created at: May 1, 2026, 12:57 a.m.