Triple
T6586368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Babylon system |
E159234
|
entity |
| Predicate | goalOfFollowers |
P55040
|
FINISHED |
| Object | to resist Babylon system |
—
|
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: to resist Babylon system | Statement: [Babylon system, goalOfFollowers, to resist Babylon system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalOfFollowers Context triple: [Babylon system, goalOfFollowers, to resist Babylon system]
-
A.
layFollowers
Indicates that one entity is a non-ordained (lay) follower or adherent of another entity, typically a religious figure, institution, or tradition.
-
B.
followerOf
Indicates that one entity subscribes to, tracks, or regularly receives updates from another entity, typically in a social or informational context.
-
C.
followsObjective
chosen
Indicates that one entity pursues, adheres to, or acts in accordance with the goal, plan, or objective defined by another entity.
-
D.
followerEvent
Indicates that one entity begins or performs the action of following another entity, typically recorded as a discrete event in time.
-
E.
hasFollowers
Indicates that an entity is followed or subscribed to by one or more other entities.
- 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_69c688366ce8819083f8883983c0df92 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6c07cdf048190945ca5810fb1de88 |
completed | March 27, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c6acfb462481909cb7aff5af4bca9d |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:54 p.m.