Triple
T35250322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISS Enterprise |
E1018075
|
entity |
| Predicate | hasBrig |
P187086
|
FINISHED |
| Object | detention area for prisoners |
—
|
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: detention area for prisoners | Statement: [ISS Enterprise, hasBrig, detention area for prisoners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBrig Context triple: [ISS Enterprise, hasBrig, detention area for prisoners]
-
A.
hasBridgeTo
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
-
B.
hasBrowridge
Indicates that one entity possesses a brow ridge feature in relation to another (typically a morphological or anatomical association).
-
C.
hasShipRig
Indicates that an entity is equipped with, or characterized by, a particular type of ship rigging configuration.
-
D.
hasBroad
Indicates that one entity possesses or exhibits a wide or extensive scope, range, or coverage in relation to another entity or context.
-
E.
hasBracing
Indicates that one entity is structurally supported, reinforced, or stabilized by another entity acting as bracing.
- 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_69f76de407d081909dfc3c419817ae93 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb3424724c8190ba55ecf66fa0b171 |
completed | May 6, 2026, 12:29 p.m. |
Created at: May 3, 2026, 4:02 p.m.