Triple
T224322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shinto |
E4281
|
entity |
| Predicate | associatedWithSymbol |
P2830
|
FINISHED |
| Object | torii gate |
—
|
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: torii gate | Statement: [Shinto, associatedWithSymbol, torii gate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithSymbol Context triple: [Shinto, associatedWithSymbol, torii gate]
-
A.
isAssociatedWith
chosen
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
B.
associatedWithVerb
Indicates that one entity is connected or linked to another through some verb-based relationship or action.
-
C.
associatedWithMovement
Indicates a relationship where an entity is connected to, involved in, or influenced by a particular movement (e.g., social, political, artistic, or ideological).
-
D.
notablyAssociatedWith
Indicates that one entity is prominently or distinctively connected with another in a way that is especially noteworthy or remarkable.
-
E.
organizationAssociatedWith
Indicates that there is a formal or recognized connection or affiliation between an organization and 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25dec53ac8190912f3d79576131fa |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b5739dc8190bad8bfa330ce0499 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.