Triple
T25638459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praxidike |
E642769
|
entity |
| Predicate | isCapturedObject |
P4712
|
FINISHED |
| Object | likely |
—
|
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: likely | Statement: [Praxidike, isCapturedObject, likely]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCapturedObject Context triple: [Praxidike, isCapturedObject, likely]
-
A.
isLikelyCapturedObject
Indicates that an entity is probably the object (receiver) of a capturing action or event in a given context.
-
B.
capturedFor
Indicates that one entity has been taken into custody, control, or possession specifically for the benefit, use, or purpose of another entity.
-
C.
capturedUsing
Indicates that something was recorded, obtained, or documented by means of a specified tool, method, or device.
-
D.
capturedIn
Indicates that one entity was taken prisoner, seized, or otherwise brought under control within the context, location, or event represented by another entity.
-
E.
capturedBy
chosen
Indicates that one entity has been seized, taken into control, or otherwise apprehended by 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fa64332081909df65f8b4380f152 |
completed | May 2, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 5:37 p.m.