Triple
T36834808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Okada Manila |
E910240
|
entity |
| Predicate | hasSuiteType |
P16808
|
FINISHED |
| Object | villa |
—
|
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: villa | Statement: [Okada Manila, hasSuiteType, villa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuiteType Context triple: [Okada Manila, hasSuiteType, villa]
-
A.
containsSuite
Indicates that one entity includes or encompasses a suite (a set or collection of related items, components, or units) as part of its contents.
-
B.
hasSuiteLevel
Indicates that one entity is associated with a specific floor or level within a suite or multi-level unit.
-
C.
haveType
chosen
Indicates that an entity belongs to or is classified under a specified type or category.
-
D.
hasSuit
Indicates that an entity possesses, wears, or is associated with a particular suit (such as clothing, armor, or a formal outfit).
-
E.
hasParentProductSuite
Indicates that a product belongs to or is contained within a higher-level parent product suite.
- 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a002962f6e081909906d6436bae6407 |
completed | May 10, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_6a00284c9c7c8190a77f18a41eee55df |
completed | May 10, 2026, 6:40 a.m. |
Created at: May 3, 2026, 4:13 p.m.