Triple
T32892031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cruise Origin |
E841358
|
entity |
| Predicate | entryConfiguration |
P175554
|
FINISHED |
| Object | side sliding doors |
—
|
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: side sliding doors | Statement: [Cruise Origin, entryConfiguration, side sliding doors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entryConfiguration Context triple: [Cruise Origin, entryConfiguration, side sliding doors]
-
A.
entryControl
Indicates a relationship where one entity regulates or authorizes another entity’s access to a place, system, or resource.
-
B.
entryMode
Indicates the manner or method by which something is entered, recorded, or input into a system or context.
-
C.
entryCondition
Indicates the prerequisite state, criteria, or circumstances that must be satisfied before entering or initiating a particular process, state, or context.
-
D.
entryDefinition
Indicates that something serves as the formal definition or descriptive specification of a particular entry or record.
-
E.
entryDescription
Indicates that a text provides a descriptive summary or explanation of a particular entry or record.
- 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d210fc80819091ed8961aa2cddfb |
completed | May 3, 2026, 4:41 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d16b79dc8190ab0d4657f2ef9a5b |
completed | May 3, 2026, 4:39 a.m. |
Created at: May 1, 2026, 1:18 a.m.