Triple
T18952897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sky Ladder |
E463698
|
entity |
| Predicate | structureForm |
P11599
|
FINISHED |
| Object | ladder |
—
|
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: ladder | Statement: [Sky Ladder, structureForm, ladder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: structureForm Context triple: [Sky Ladder, structureForm, ladder]
-
A.
typicalForm
Indicates that one entity represents the standard, characteristic, or most common form or shape in which another entity typically appears or is realized.
-
B.
formsFor
Indicates that one entity constitutes the physical or structural makeup of another entity.
-
C.
filingForm
Indicates that an entity submits or completes a specific form or document, typically as part of an official or administrative process.
-
D.
visualForm
chosen
Indicates the visual appearance, shape, or structural pattern that characterizes how something looks.
-
E.
referenceForm
Indicates that one entity serves as a reference or canonical form for another entity, typically used as the standard or authoritative version to which others relate.
- 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d544fef8819091147189ddd89617 |
completed | April 20, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon