Triple
T21738366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Project Phoenix |
E536584
|
entity |
| Predicate | searchBand |
P145176
|
FINISHED |
| Object | microwave radio frequencies |
—
|
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: microwave radio frequencies | Statement: [Project Phoenix, searchBand, microwave radio frequencies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: searchBand Context triple: [Project Phoenix, searchBand, microwave radio frequencies]
-
A.
byBandOrGroup
Indicates that something (such as a work, performance, or recording) is created, performed, or produced by a specific band or musical group.
-
B.
sharesBandWith
Indicates that two entities are members of at least one of the same musical bands.
-
C.
bands
Indicates that multiple entities join together to form a group or collective unit.
-
D.
musicGroupFounded
Indicates the relationship where a music group is established or created at a specific time or by a particular founder or entity.
-
E.
hasBand
Indicates that an entity is associated with or includes a particular band (e.g., musical group or band-like unit).
- F. None of above. chosen
Provenance (4 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_69e0c46df5448190b4322127ffc4c690 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69effd0e94c4819096bace0c661f5156 |
completed | April 28, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69f3ed4408190a4a78410bf660c44 |
completed | April 20, 2026, 9:48 p.m. |
Created at: April 16, 2026, 6:49 p.m.