Triple
T35804153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 金鯱 |
E1035061
|
entity |
| Predicate | 機能（信仰的） |
P115228
|
FINISHED |
| Object | 火災から城を守ると信じられていた |
—
|
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: 火災から城を守ると信じられていた | Statement: [金鯱, 機能（信仰的）, 火災から城を守ると信じられていた]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 機能（信仰的） Context triple: [金鯱, 機能（信仰的）, 火災から城を守ると信じられていた]
-
A.
religiousFunction
Indicates that one entity serves a religious role, purpose, or function in relation to another entity.
-
B.
functionInBeliefSystem
chosen
Indicates that one entity serves a particular role, purpose, or function within the structure or doctrine of a belief system.
-
C.
أصل_ديني
Indicates a religious origin or affiliation that an entity belongs to or is derived from.
-
D.
theologicalAttribute
Indicates that one entity possesses or is characterized by a particular theological property, quality, or doctrinal attribute in relation to another.
-
E.
biblicalFunction
Indicates that one entity serves a particular role, duty, or purpose in a biblical or scriptural context in relation to another entity.
- 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_69f76e169bd081909f16cd8c9ee7870c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a283388c81908e4a9ee3369e8d6f |
completed | May 3, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.