Triple
T35561698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kōga ninja |
E1027651
|
entity |
| Predicate | sharesReputationWith |
P199921
|
FINISHED |
| Object | Iga ninja |
—
|
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: Iga ninja | Statement: [Kōga ninja, sharesReputationWith, Iga ninja]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesReputationWith Context triple: [Kōga ninja, sharesReputationWith, Iga ninja]
-
A.
sharesCreditWith
Indicates that two or more entities are jointly acknowledged or recognized for the same contribution, achievement, or work.
-
B.
commonReputation
chosen
Indicates that multiple entities share the same reputation or are commonly regarded in a similar way by others.
-
C.
hasReputationAmong
Indicates that an entity is regarded or perceived in a particular way by a specified group or audience.
-
D.
associatedWithReputation
Indicates a relationship where an entity is linked to, influenced by, or characterized in terms of another entity’s reputation or perceived standing.
-
E.
tributeAssessmentReputation
Indicates the evaluation of an entity’s reputation specifically in the context of determining or justifying a tribute assessment.
- 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0067cde0f08190b2cd93af5f00d519 |
completed | May 10, 2026, 11:11 a.m. |
| PD | Predicate disambiguation | batch_6a0065820c8c8190994734433c64a30a |
completed | May 10, 2026, 11:01 a.m. |
Created at: May 3, 2026, 4:04 p.m.