Triple
T3865021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kamakura period |
E91830
|
entity |
| Predicate | dominantClass |
P51552
|
FINISHED |
| Object | samurai |
—
|
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: samurai | Statement: [Kamakura period, dominantClass, samurai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantClass Context triple: [Kamakura period, dominantClass, samurai]
-
A.
dominantForm
Indicates that one form, type, or variant is the primary or most prevalent version relative to others in a given context.
-
B.
dominantFormOf
Indicates that one form of something is the primary, prevailing, or most influential version relative to another form.
-
C.
dominantOn
Indicates that one entity exerts control, authority, or prevailing influence over another in a given context.
-
D.
dominantDuring
Indicates that one entity holds a prevailing or controlling influence over another specifically within a given time period or interval.
-
E.
dominantTree
Indicates that one tree has a dominant or prevailing influence over another tree, such as in size, canopy coverage, or competitive advantage within a shared environment.
- 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_69aed9645f348190a9868e7cef56ab7e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec3a253c81909df7dc0422ff7989 |
completed | March 9, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69aee754dddc8190936e1f9c40a770db |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aee80858a481909961a33fb50ff8d1 |
completed | March 9, 2026, 3:32 p.m. |
Created at: March 9, 2026, 3:19 p.m.