Triple
T27735484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ManualResetEvent |
E697517
|
entity |
| Predicate | hasBaseProperty |
P23698
|
FINISHED |
| Object | Handle |
—
|
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: Handle | Statement: [ManualResetEvent, hasBaseProperty, Handle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBaseProperty Context triple: [ManualResetEvent, hasBaseProperty, Handle]
-
A.
hasBaseField
Indicates that one entity serves as the foundational or underlying field structure upon which another entity is defined or constructed.
-
B.
haveProperty
chosen
Indicates that an entity possesses, exhibits, or is characterized by a particular property or attribute.
-
C.
hasBaseState
Indicates that an entity is associated with or derived from a specified fundamental or default state.
-
D.
hasSupportBaseIn
Indicates that one entity maintains an operational or organizational base of support located in another entity.
-
E.
hasSupportBase
Indicates that one entity serves as the supporting base or foundation upon which another entity rests, is mounted, or is structurally stabilized.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 27, 2026, 3:12 p.m.