Triple
T72037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PlumpJack Group |
E1441
|
entity |
| Predicate | hasPropertyType |
P3586
|
FINISHED |
| Object | resort hotel |
—
|
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: resort hotel | Statement: [PlumpJack Group, hasPropertyType, resort hotel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPropertyType Context triple: [PlumpJack Group, hasPropertyType, resort hotel]
-
A.
hasTypeName
Indicates that an entity is associated with a specific type name used to classify or identify its kind.
-
B.
hasRecordType
Indicates that an entity is associated with or classified under a specific type or category of record.
-
C.
hasModelType
Indicates that an entity is associated with or classified under a specific model type.
-
D.
hasStructureType
Indicates that an entity possesses or is classified by a specific structural type or configuration.
-
E.
hasMemberType
Indicates that an entity includes or is associated with members belonging to a specified type or category.
- 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_69a24c06b3bc8190aa4ac89026115efc |
completed | Feb. 28, 2026, 1:59 a.m. |
| NER | Named-entity recognition | batch_69a24f6997c081908b202f937eb2b14f |
completed | Feb. 28, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69a24eab7f408190a8275cb82474f575 |
completed | Feb. 28, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69a24f65170c8190bc541c8351456a4d |
completed | Feb. 28, 2026, 2:13 a.m. |
Created at: Feb. 28, 2026, 2:03 a.m.