Triple
T35012608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lilmoth |
E1009970
|
entity |
| Predicate | hasGuildPresence |
P182806
|
FINISHED |
| Object | Mages Guild |
—
|
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: Mages Guild | Statement: [Lilmoth, hasGuildPresence, Mages Guild]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGuildPresence Context triple: [Lilmoth, hasGuildPresence, Mages Guild]
-
A.
globalPresence
Indicates that an entity operates, is represented, or has a significant footprint across multiple countries or world regions.
-
B.
UNPresence
Indicates the presence, involvement, or deployment of United Nations personnel, missions, or operations in relation to an entity or location.
-
C.
maintainedPresence
Indicates that an entity continuously remained in or kept an ongoing presence within a particular context, location, or situation over a period of time.
-
D.
hasHumanPresence
Indicates that humans are physically present in or occupying a given location, object, or context.
-
E.
scenePresence
Indicates that an entity is present or appears within a particular scene or context.
- F. None of above. chosen
Provenance (4 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7908ec35881909a42f954fb9fa16e |
completed | May 3, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78fd3fd888190b7db0b563f298585 |
completed | May 3, 2026, 6:11 p.m. |
Created at: May 3, 2026, 4:01 p.m.