Triple
T35293166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cloudrest |
E1019284
|
entity |
| Predicate | mechanicFeature |
P48192
|
FINISHED |
| Object | portal phases |
—
|
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: portal phases | Statement: [Cloudrest, mechanicFeature, portal phases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mechanicFeature Context triple: [Cloudrest, mechanicFeature, portal phases]
-
A.
featuresMechanic
chosen
Indicates that something includes or incorporates a particular mechanic as part of its design or functionality.
-
B.
hasMechanicalFeature
Indicates that one entity possesses, includes, or is characterized by a specific mechanical component, attribute, or functionality.
-
C.
mechanicalExpertise
Indicates that one entity possesses specialized knowledge or skill in understanding, operating, or repairing mechanical systems or devices in relation to another entity or context.
-
D.
bodyworkFeature
Indicates a relationship where a vehicle or object possesses a specific characteristic or component of its external body structure.
-
E.
mechanicalFunction
Indicates that one entity serves as the mechanical role, operation, or function performed by another entity or system.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7901ae65c819092f17f92d7b2e561 |
completed | May 3, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.