Triple
T18989650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Issohadores |
E464647
|
entity |
| Predicate | captureTarget |
P106453
|
FINISHED |
| Object | spectators |
—
|
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: spectators | Statement: [Issohadores, captureTarget, spectators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: captureTarget Context triple: [Issohadores, captureTarget, spectators]
-
A.
acquisitionTarget
Indicates that one entity is the intended or actual company or asset being acquired by another in a merger or acquisition transaction.
-
B.
aimsToCapture
chosen
Indicates an intention or effort by one entity to take control of, seize, or gain possession of another entity.
-
C.
target
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
D.
captureType
Indicates the manner or method by which something is captured, recorded, or acquired in the context of the relationship.
-
E.
capturedFor
Indicates that one entity has been taken into custody, control, or possession specifically for the benefit, use, or purpose of another entity.
- 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_69d8dd01a56c81909694a128c66b21d7 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d66272388190850a7e5dec165a01 |
completed | April 20, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f88e0c81908cb20f08bf24cd32 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:01 p.m.