Triple
T129661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Booz Allen Hamilton |
E2625
|
entity |
| Predicate | hasClientSector |
P2193
|
FINISHED |
| Object | defense |
—
|
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: defense | Statement: [Booz Allen Hamilton, hasClientSector, defense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClientSector Context triple: [Booz Allen Hamilton, hasClientSector, defense]
-
A.
hasClient
Indicates that an entity maintains a client relationship with another entity, typically as a provider of goods or services.
-
B.
sectorServed
chosen
Indicates the industry or economic sector that an entity primarily serves or targets with its activities, products, or services.
-
C.
hasStakeholder
Indicates that an entity is a stakeholder of another entity, typically having an interest, involvement, or influence in its activities or outcomes.
-
D.
hasMarketParticipants
Indicates that a market or trading venue involves or is associated with specific participating entities (such as buyers, sellers, or intermediaries).
-
E.
hasTypeOfOrganization
Indicates that an entity is classified as belonging to a particular type or category of organization.
- 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_69a2520c0f3481908b0ed054a2fca8d0 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a2576518e0819096b35d8af7a4d1bd |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a2564da96c8190aa8204de25229c15 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:30 a.m.