Triple
T25232447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jumboo Savari |
E632249
|
entity |
| Predicate | hasSecurityArrangements |
P92827
|
FINISHED |
| Object | large-scale |
—
|
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: large-scale | Statement: [Jumboo Savari, hasSecurityArrangements, large-scale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecurityArrangements Context triple: [Jumboo Savari, hasSecurityArrangements, large-scale]
-
A.
securityArrangementsBy
Indicates that one entity is responsible for providing, organizing, or overseeing security arrangements for another entity or situation.
-
B.
securityArrangements
chosen
Indicates the existence, nature, or details of protective measures or safeguards established between or around entities.
-
C.
hasSecurityRegime
Indicates that an entity is governed, protected, or controlled by a particular security regime, framework, or set of security rules.
-
D.
hasSecurityPresence
Indicates that some form of security personnel, system, or measures are present at or associated with an entity or location.
-
E.
hasHighSecurityFacility
Indicates that an entity possesses or operates a facility characterized by a high level of security measures and protections.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 21, 2026, 1:06 p.m.