Triple
T30871557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irmo, South Carolina |
E786355
|
entity |
| Predicate | OkraStrutFeatures |
P80690
|
FINISHED |
| Object | parade |
—
|
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: parade | Statement: [Irmo, South Carolina, OkraStrutFeatures, parade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: OkraStrutFeatures Context triple: [Irmo, South Carolina, OkraStrutFeatures, parade]
-
A.
featuresStructure
Indicates that one entity possesses, exhibits, or incorporates a particular structure as a notable characteristic or component.
-
B.
featuresIn
chosen
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
-
C.
shellFeature
Indicates that one entity functions as a characteristic or structural feature of another entity’s shell.
-
D.
featuresOrchestrationBy
Indicates that something (such as a work, event, or performance) is characterized by or includes orchestration carried out by a particular agent or entity.
-
E.
configurationFeatures
Indicates the specific options or characteristics that are enabled or defined within a particular configuration.
- 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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f691d1c75c8190a447d06787e5e2ae |
completed | May 3, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:48 p.m.