Triple
T33046819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cloelia |
E845617
|
entity |
| Predicate | choseToFree |
P7321
|
FINISHED |
| Object | young Roman boys |
—
|
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: young Roman boys | Statement: [Cloelia, choseToFree, young Roman boys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: choseToFree Context triple: [Cloelia, choseToFree, young Roman boys]
-
A.
freeRelease
Indicates that one entity releases another from an obligation, constraint, or state without requiring payment or compensation.
-
B.
freeFrom
Indicates that one entity does not contain, is not affected by, or is exempt from another specified entity, condition, or constraint.
-
C.
freedBy
chosen
Indicates that an entity is released or liberated as a result of an action performed by another entity.
-
D.
freedomCondition
Indicates the conditions or circumstances under which an entity is considered free or granted freedom.
-
E.
willBreakFreeDuring
Indicates that an entity is expected to escape or become free from another entity or constraint during a specified time or event.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:24 a.m.