Triple
T20522174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harmony |
E503836
|
entity |
| Predicate | assemblyRole |
P79768
|
FINISHED |
| Object | enabled attachment of Columbus |
—
|
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: enabled attachment of Columbus | Statement: [Harmony, assemblyRole, enabled attachment of Columbus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assemblyRole Context triple: [Harmony, assemblyRole, enabled attachment of Columbus]
-
A.
roleInAssembly
chosen
Indicates the specific function, position, or responsibility an entity holds within a particular assembly or gathering.
-
B.
codeRole
Indicates a relationship where an entity serves a specific role or function within a piece of code or software system.
-
C.
encodingRole
Indicates the role or function an entity has in the process of encoding information into a particular form or representation.
-
D.
roleInCommandStructure
Indicates that one entity holds a specific position or function within the hierarchical command structure of another entity or organization.
-
E.
unitRole
Indicates the functional role or purpose that a unit serves within a larger system or 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_69e0b4b3a6e08190ae663701f50fab8e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69f46488c819093687b4e07837793 |
completed | April 20, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:36 a.m.