Triple
T31190885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Animal Liberation Front |
E795176
|
entity |
| Predicate | hasNotableOperationType |
P20911
|
FINISHED |
| Object | laboratory break-ins |
—
|
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: laboratory break-ins | Statement: [Animal Liberation Front, hasNotableOperationType, laboratory break-ins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableOperationType Context triple: [Animal Liberation Front, hasNotableOperationType, laboratory break-ins]
-
A.
hasNotableOperation
Indicates that an entity is associated with a significant or noteworthy operation, activity, or procedure.
-
B.
hasOperationType
Indicates the specific kind or category of operation associated with an entity or process.
-
C.
notableOperationType
chosen
Indicates that an entity is associated with a specific type or category of operation that is considered notable or significant.
-
D.
hasNotableType
Indicates that an entity is associated with a specific notable category or type that characterizes its significance or role.
-
E.
hasOperationsIn
Indicates that an entity conducts business activities or maintains operational presence within a specified location or region.
- 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_69f224d7a6a481908187c4362a8a525f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a0082989e6c819099fea0e706332e37 |
completed | May 10, 2026, 1:05 p.m. |
| PD | Predicate disambiguation | batch_6a0081ed6a1481908baf472876e28db9 |
completed | May 10, 2026, 1:02 p.m. |
Created at: April 29, 2026, 9:08 p.m.