Triple
T3202521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allegro |
E67082
|
entity |
| Predicate | approximatePerformanceCount |
P20922
|
FINISHED |
| Object | 315 |
—
|
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: 315 | Statement: [Allegro, approximatePerformanceCount, 315]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximatePerformanceCount Context triple: [Allegro, approximatePerformanceCount, 315]
-
A.
runtimeApprox
Indicates an approximate or estimated duration of time that something (such as a process, program, or event) takes to run or complete.
-
B.
runsApproximately
Indicates that an entity performs a running action in a manner that is close to, but not exactly matching, a specified time, distance, speed, or other running-related measure.
-
C.
hasApproximateNumberOfMusicians
chosen
Indicates that an entity is associated with an estimated or approximate count of musicians involved with it.
-
D.
hasApproximateVendorCount
Indicates that an entity is associated with an estimated or non-exact number of vendors.
-
E.
roundsFiredEstimate
Indicates an estimated number of shots or rounds that have been fired in a given context or event.
- 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_69ad8589bd988190afa7ed2bdffb7b33 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada9b046c8819087c0a61c4f9adeb7 |
completed | March 8, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69ad9e078f7c8190813d9fcb4f5071fb |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.