Triple
T6921136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neque semper arcum tendit Apollo |
E160186
|
entity |
| Predicate | objectOfVerb |
P73670
|
FINISHED |
| Object | arcum |
—
|
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: arcum | Statement: [Neque semper arcum tendit Apollo, objectOfVerb, arcum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: objectOfVerb Context triple: [Neque semper arcum tendit Apollo, objectOfVerb, arcum]
-
A.
associatedWithVerb
Indicates that one entity is connected or linked to another through some verb-based relationship or action.
-
B.
grammaticalPersonOfVerb
Indicates the grammatical person (first, second, or third person) associated with a given verb form.
-
C.
hasVerbAspect
Indicates that a verb or verbal expression is associated with a particular grammatical aspect (such as perfective, imperfective, or progressive) describing the temporal structure of the action or state.
-
D.
nounFormOf
Indicates that one term is the noun form derived from, or corresponding to, another term (typically a verb or adjective).
-
E.
hasVerbClass
Indicates that an action or event is categorized into a specific verb class based on its grammatical or semantic behavior.
- F. None of above. chosen
Provenance (4 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_69c6884d350081908d8a970e4d40ad78 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9fb8ac48190b50bbc47fad8288f |
completed | March 27, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bb577c81908ee8b415b4281f3d |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d98625c88190a37fdf6d95d7fcbd |
completed | March 27, 2026, 7:24 p.m. |
Created at: March 27, 2026, 2:26 p.m.