Triple
T9819028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nakagin Capsule Tower |
E238479
|
entity |
| Predicate | capsuleAttachmentMethod |
P42077
|
FINISHED |
| Object | high-tension bolts |
—
|
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: high-tension bolts | Statement: [Nakagin Capsule Tower, capsuleAttachmentMethod, high-tension bolts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capsuleAttachmentMethod Context triple: [Nakagin Capsule Tower, capsuleAttachmentMethod, high-tension bolts]
-
A.
capsule
Indicates that one entity is a capsule containing, enclosing, or encapsulating another entity.
-
B.
capsuleSystem
Indicates a relationship where an entity functions as or belongs to a capsule-based system (e.g., a system organized around or implemented via capsules).
-
C.
attachmentMethod
chosen
Indicates the way or technique by which one entity is fastened, joined, or secured to another.
-
D.
capsuleName
Indicates that an entity has the specified name or label of a capsule (such as a pill, container, or encapsulated unit).
-
E.
attachedTo
Indicates that one entity is physically or logically fastened, connected, or joined to another entity.
- 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_69ca84dfde1481909f47c286d715f892 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb2f74e348190be8e4394ae6fe3fe |
completed | April 2, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cd03e01ea881909a7d93fc3994ace5 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:31 p.m.