Triple
T21094859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ravenel Bridge |
E519735
|
entity |
| Predicate | cableArrangement |
P88377
|
FINISHED |
| Object | fan |
—
|
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: fan | Statement: [Ravenel Bridge, cableArrangement, fan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cableArrangement Context triple: [Ravenel Bridge, cableArrangement, fan]
-
A.
hasCableArrangement
chosen
Indicates that one entity is connected to or equipped with another entity through a specific configuration or layout of cables.
-
B.
cableEnd
Indicates that one entity represents an endpoint or terminal position of a cable in relation to another entity.
-
C.
cableType
Indicates the specific kind or category of cable associated with or used by an entity.
-
D.
hasNumberOfCables
Indicates the relationship that specifies how many cables are associated with a given entity.
-
E.
needleArrangement
Indicates how needles are positioned or organized relative to each other in a given context.
- 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_69e0b508d8dc81909be940dafe36c8f7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e709517a18819081ede1d38e2c4391 |
completed | April 21, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:52 p.m.