Triple
T25974909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alfredo Garcia |
E645908
|
entity |
| Predicate | objectOfSearchBy |
P135262
|
FINISHED |
| Object | bounty hunters |
—
|
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: bounty hunters | Statement: [Alfredo Garcia, objectOfSearchBy, bounty hunters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: objectOfSearchBy Context triple: [Alfredo Garcia, objectOfSearchBy, bounty hunters]
-
A.
typeOfSearch
Indicates the specific kind or category of search operation being performed or requested between entities.
-
B.
searchingFor
Indicates that one entity is actively seeking, looking for, or attempting to locate another entity.
-
C.
objectOfQuest
chosen
Indicates that one entity is the target, goal, or item being sought or pursued in another entity’s quest or mission.
-
D.
searchOrderedBy
Indicates that a search operation is performed and the resulting items are arranged according to a specified ordering criterion.
-
E.
searchesVia
Indicates that an entity performs a search by means of, or using, a specified tool, method, or channel.
- 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_69e77e8768648190b27bb578f14bcb88 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f60c698ae48190871cd445422bad91 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 22, 2026, 8:51 a.m.