Triple
T29139738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blam! engine |
E738590
|
entity |
| Predicate | AIFeature |
P40827
|
FINISHED |
| Object | squad-based AI behaviors |
—
|
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: squad-based AI behaviors | Statement: [Blam! engine, AIFeature, squad-based AI behaviors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AIFeature Context triple: [Blam! engine, AIFeature, squad-based AI behaviors]
-
A.
auxiliaryFeature
Indicates that one feature functions as a secondary or supporting capability to another primary feature.
-
B.
featuresSample
Indicates that an entity includes or presents a particular sample as one of its components or examples.
-
C.
featureSet
chosen
Indicates that one entity is a collection or configuration of features associated with or applied to another entity.
-
D.
targetFeature
Indicates that one entity is the specific feature, attribute, or characteristic that another entity is directed toward, focused on, or intended to affect.
-
E.
featuresCreator
Indicates that an entity prominently presents, highlights, or showcases a particular creator as a key associated party.
- 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6626dee588190ae10942e2a9bff64 |
completed | May 2, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:36 a.m.