Triple
T21844759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Itinerarium mentis in Deum |
E539345
|
entity |
| Predicate | containsNumberOfStages |
P7615
|
FINISHED |
| Object | seven stages |
—
|
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: seven stages | Statement: [Itinerarium mentis in Deum, containsNumberOfStages, seven stages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsNumberOfStages Context triple: [Itinerarium mentis in Deum, containsNumberOfStages, seven stages]
-
A.
numberOfStages
chosen
Indicates the total count of distinct stages or phases associated with a given process, event, or entity.
-
B.
numberPerStage
Indicates the quantity or count associated with each distinct stage in a multi-stage process or sequence.
-
C.
hasStageStructure
Indicates that one entity possesses or is characterized by a particular stage-based structural organization defined by another entity.
-
D.
hasStageType
Indicates that an entity is associated with, or classified by, a specific type or category of stage within a process, lifecycle, or workflow.
-
E.
hasFinalStage
Indicates that an entity possesses or reaches a concluding or ultimate phase in a process, sequence, or lifecycle.
- 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_69e0c476c3c88190a92d08ebb59a128a |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0bd5398fc81909f025bcccd0f80cb |
completed | April 28, 2026, 1:59 p.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:55 p.m.