Triple
T24184303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reel of Tulloch |
E599510
|
entity |
| Predicate | formationFeature |
P23125
|
FINISHED |
| Object | dancers arranged in a circle |
—
|
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: dancers arranged in a circle | Statement: [Reel of Tulloch, formationFeature, dancers arranged in a circle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formationFeature Context triple: [Reel of Tulloch, formationFeature, dancers arranged in a circle]
-
A.
namedFeature
Indicates that an entity has a specific feature or attribute that is explicitly given a name.
-
B.
formsFeature
Indicates that one entity constitutes or creates a characteristic, component, or distinguishing element of another entity.
-
C.
formationType
chosen
Indicates the specific structural or organizational configuration in which something is arranged, created, or formed.
-
D.
metricalFeature
Indicates a relationship where one entity specifies or characterizes a metrical property or pattern of another entity.
-
E.
surfaceFeatureOf
Indicates that one entity is a surface-level characteristic, pattern, or feature belonging to or present on 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_69e288cca05481908faeb1563711114a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:35 p.m.