Triple
T36704238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | word2vec |
E906310
|
entity |
| Predicate | exampleProperty |
P186181
|
FINISHED |
| Object | king - man + woman ≈ queen |
—
|
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: king - man + woman ≈ queen | Statement: [word2vec, exampleProperty, king - man + woman ≈ queen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exampleProperty Context triple: [word2vec, exampleProperty, king - man + woman ≈ queen]
-
A.
typicalProperty
Indicates that a certain property is characteristically or commonly associated with an entity, reflecting what is typical for that entity.
-
B.
propertyForm
Indicates the specific form, type, or configuration that a property takes within a given context or system.
-
C.
studiedProperty
Indicates that an entity has examined, researched, or analyzed a particular property or attribute of another entity.
-
D.
ownedProperty
Indicates that one entity possesses legal ownership or control over another entity as property.
-
E.
basisProperty
Indicates that one property serves as the foundational or defining basis for another property or characteristic.
- 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_69f76e7195c48190b5580c9cfb01e95f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:12 p.m.