Triple
T28572390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laamb |
E723147
|
entity |
| Predicate | involvesStriking |
P144377
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Laamb, involvesStriking, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesStriking Context triple: [Laamb, involvesStriking, true]
-
A.
usesStrikes
Indicates that one entity employs or relies on strikes as a method, tactic, or means to achieve a goal or exert influence over another entity or situation.
-
B.
strikingAllowed
Indicates that performing a physical strike (e.g., hitting or attacking) on the target entity is permitted under the given rules or conditions.
-
C.
strikeAction
chosen
Indicates an action where one entity forcefully hits, attacks, or impacts another entity.
-
D.
notableStrike
Indicates that an entity is recognized for having carried out or been involved in a particularly significant or impactful strike (such as a labor strike, military strike, or similar major action).
-
E.
typeOfStrike
Indicates the specific category or kind of strike involved in an event or action.
- 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_69f01d7e97708190ae9e77ee66a68abd |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 28, 2026, 4:10 a.m.