Triple
T29541587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caecilius |
E749514
|
entity |
| Predicate | hasFreedmanForm |
P173733
|
FINISHED |
| Object | Caecilius L. l. |
—
|
NE NERFINISHED |
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: Caecilius L. l. | Statement: [Caecilius, hasFreedmanForm, Caecilius L. l.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFreedmanForm Context triple: [Caecilius, hasFreedmanForm, Caecilius L. l.]
-
A.
hasAidForm
Indicates that one entity provides or is associated with a particular form or type of aid related to another entity.
-
B.
hasSubjectMatterForm
Indicates that something (such as a work, resource, or record) is associated with a particular form or type of subject matter it deals with.
-
C.
hasDecisionForm
Indicates that an entity is associated with, or represented by, a particular decision document or formal decision record.
-
D.
hasFamilialForm
Indicates that one entity has a version, variant, or form that is specifically used in familial or family-related contexts in relation to another entity.
-
E.
hasPracticeForm
Indicates that an entity is associated with, or takes place in, a particular form or mode of practice.
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f6b9a84ff88190ab5a71f7ef1e0dac |
completed | May 3, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b8fe147881908ba17483c7b13f05 |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 28, 2026, 5:03 p.m.