Triple
T31659512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Team |
E807959
|
entity |
| Predicate | organizationTypePromoted |
P181449
|
FINISHED |
| Object | armed forces |
—
|
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: armed forces | Statement: [Army Team, organizationTypePromoted, armed forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizationTypePromoted Context triple: [Army Team, organizationTypePromoted, armed forces]
-
A.
promotedOrganization
Indicates that one entity actively markets, advertises, or otherwise promotes another organization.
-
B.
promotedIdentity
Indicates that one entity has actively supported, elevated, or publicized the status, visibility, or recognition of another entity’s identity.
-
C.
hasBeenPromotedBy
Indicates that one entity has received a promotion as a result of the decision or action taken by another entity.
-
D.
promotedFrom
Indicates that an entity has advanced to a new position, role, or status from a specified prior one.
-
E.
promotedWith
Indicates that one entity is advertised, marketed, or publicized together with another entity as part of the same promotional effort.
- 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69f77648979c8190b6cdbb835ab8987c |
completed | May 3, 2026, 4:22 p.m. |
Created at: April 30, 2026, 10:56 p.m.