Triple
T37357073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corrente |
E927482
|
entity |
| Predicate | hasRoleInSuite |
P161
|
FINISHED |
| Object | second or third movement |
—
|
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: second or third movement | Statement: [Corrente, hasRoleInSuite, second or third movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoleInSuite Context triple: [Corrente, hasRoleInSuite, second or third movement]
-
A.
containsSuite
Indicates that one entity includes or encompasses a suite (a set or collection of related items, components, or units) as part of its contents.
-
B.
hasNameInSuite
Indicates that an entity has a specific name or label as used within a particular suite or collection context.
-
C.
alsoInSuiteWith
Indicates that one entity is part of the same suite, set, or grouped collection as another entity.
-
D.
hasRole
chosen
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
-
E.
hasSuiteLevel
Indicates that one entity is associated with a specific floor or level within a suite or multi-level unit.
- 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fee25dbca481909e6f1c255122b3a8 |
completed | May 9, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69fee1c8915c8190b08b63e42881f1a9 |
completed | May 9, 2026, 7:27 a.m. |
Created at: May 3, 2026, 4:16 p.m.