Triple
T13543813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crescite et Multiplicamini |
E323458
|
entity |
| Predicate | containsConjunction |
P51086
|
FINISHED |
| Object | et |
—
|
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: et | Statement: [Crescite et Multiplicamini, containsConjunction, et]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsConjunction Context triple: [Crescite et Multiplicamini, containsConjunction, et]
-
A.
hasConjunction
chosen
Indicates that two or more entities are linked together by a coordinating conjunction, forming a combined or joint relationship.
-
B.
containsCondition
Indicates that one entity includes, embodies, or is associated with a particular condition.
-
C.
junctionOf
Indicates that one or more entities meet or intersect at a common point, forming a junction between them.
-
D.
hasConjunctForms
Indicates that an entity is associated with one or more conjunct (combined or compound) forms of itself or related elements.
-
E.
includesClause
Indicates that one entity (typically a document, contract, or statement) contains or incorporates a specific clause as part of its content.
- 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae13bec4819084c1770638c00ed9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:45 p.m.