Triple
T8143364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Divided Line |
E190148
|
entity |
| Predicate | associatesPistisWith |
P2830
|
FINISHED |
| Object | physical things |
—
|
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: physical things | Statement: [Divided Line, associatesPistisWith, physical things]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatesPistisWith Context triple: [Divided Line, associatesPistisWith, physical things]
-
A.
associatedWithGod
Indicates a relationship in which an entity is linked, related, or connected in some meaningful way to a god or deity.
-
B.
isAssociatedWith
chosen
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
C.
associatedWithSacrament
Indicates a relationship where something is connected or related to a specific sacrament in a religious or ritual context.
-
D.
associatedWithBlessing
Indicates a relationship in which an entity is connected to, linked with, or characterized by a blessing or act of blessing.
-
E.
associatedWithChurch
Indicates a relationship in which an entity has a connection, involvement, or affiliation with a church.
- 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_69ca82bd9900819099477cdc2eb4244f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4444bb248190beaaa2ce4b8f3eaa |
completed | March 31, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69cb369c0d0481908762c488d7f77e74 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:36 p.m.