Triple
T29673919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crystal Cabin |
E750749
|
entity |
| Predicate | hasDifferenceFrom |
P61682
|
FINISHED |
| Object | standard cabins without glass floor |
—
|
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: standard cabins without glass floor | Statement: [Crystal Cabin, hasDifferenceFrom, standard cabins without glass floor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDifferenceFrom Context triple: [Crystal Cabin, hasDifferenceFrom, standard cabins without glass floor]
-
A.
hasDifferential
Indicates that one entity is the derivative or rate-of-change expression corresponding to another entity.
-
B.
hasLexicalDifferencesWith
Indicates that two linguistic items differ from each other in their word choice or lexical form.
-
C.
isDifferenceOf
Indicates that one quantity or entity represents the result obtained by subtracting one specified quantity or entity from another.
-
D.
differIn
chosen
Indicates that two entities are not the same in at least one specified aspect, attribute, or value.
-
E.
hasGrammarDifferenceFrom
Indicates that two linguistic items differ from each other in their grammatical form, structure, or rules of usage.
- 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_69f0d624d7b08190ba237d226f78d0d9 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: April 28, 2026, 7:06 p.m.