Triple
T38634601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highrise |
E937543
|
entity |
| Predicate | hasPopularStrategy |
P13064
|
FINISHED |
| Object | sniping from rooftop edges |
—
|
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: sniping from rooftop edges | Statement: [Highrise, hasPopularStrategy, sniping from rooftop edges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPopularStrategy Context triple: [Highrise, hasPopularStrategy, sniping from rooftop edges]
-
A.
hasCoreStrategy
Indicates that an entity possesses or is associated with a primary, central, or foundational strategy guiding its actions or decisions.
-
B.
hasStrategyType
Indicates that an entity employs, follows, or is associated with a particular type or category of strategy.
-
C.
usesStrategy
chosen
Indicates that an entity intentionally applies a particular strategy or method to achieve a goal or perform an action.
-
D.
hasRiskyStrategy
Indicates that an entity employs or is associated with a strategy characterized by a high level of risk or potential for significant loss.
-
E.
hasElectoralStrategy
Indicates that an entity employs or is associated with a specific plan or approach for winning or influencing an election.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a001adc8c108190ab3a43f6415e2be3 |
completed | May 10, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_6a001a290330819097c2c3123f9014b4 |
completed | May 10, 2026, 5:39 a.m. |
Created at: May 3, 2026, 4:32 p.m.