Triple
T17712865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simon Magus |
E441613
|
entity |
| Predicate | reputationAmong |
P61188
|
FINISHED |
| Object | people of Samaria |
—
|
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: people of Samaria | Statement: [Simon Magus, reputationAmong, people of Samaria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reputationAmong Context triple: [Simon Magus, reputationAmong, people of Samaria]
-
A.
hasReputationAmong
chosen
Indicates that an entity is regarded or perceived in a particular way by a specified group or audience.
-
B.
denotesReputationOf
Indicates that one entity represents, expresses, or serves as an indicator of the reputation or perceived standing of another entity.
-
C.
reputationInSources
Indicates that an entity has a certain reputation or standing as reflected or reported in various information sources.
-
D.
scoringReputation
Indicates that one entity evaluates and assigns a reputation-related score to another entity based on its behavior or performance.
-
E.
collectionReputation
Indicates the perceived quality, trustworthiness, or status associated with a particular collection based on others’ evaluations or interactions.
- 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4729c2c98819086fe48420217308d |
completed | April 19, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69e3cde601d4819097903f471f1fe99a |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:06 a.m.