Triple
T38588611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scarlet Monastery |
E932401
|
entity |
| Predicate | reworkResultedIn |
P374
|
FINISHED |
| Object | Scarlet Halls |
—
|
NE NERFINISHED |
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: Scarlet Halls | Statement: [Scarlet Monastery, reworkResultedIn, Scarlet Halls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reworkResultedIn Context triple: [Scarlet Monastery, reworkResultedIn, Scarlet Halls]
-
A.
reworkedBy
Indicates that an existing work, product, or result has been modified, revised, or substantially altered by a particular agent.
-
B.
result
chosen
Indicates that one entity is produced, caused, or brought about as an outcome or consequence of another entity or process.
-
C.
reformedDueTo
Indicates that one entity has changed or improved its behavior, beliefs, or practices as a result of the influence, actions, or circumstances associated with another entity.
-
D.
recreated
Indicates that an entity has been created again or restored, typically after being removed, destroyed, or significantly altered.
-
E.
laterRewrittenAs
Indicates that an earlier work, version, or expression was subsequently rewritten or replaced by a later one.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.