Triple
T20345649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gringai |
E495860
|
entity |
| Predicate | hasTraditionalTool |
P124889
|
FINISHED |
| Object | spears |
—
|
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: spears | Statement: [Gringai, hasTraditionalTool, spears]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalTool Context triple: [Gringai, hasTraditionalTool, spears]
-
A.
hasTraditionalTechnology
chosen
Indicates that an entity possesses, uses, or is associated with technology rooted in longstanding, customary, or indigenous practices rather than modern or industrial methods.
-
B.
hasTraditionalFeatures
Indicates that something possesses characteristics or attributes commonly associated with established traditions or customary practices.
-
C.
hasTraditionalBase
Indicates that something is supported by, built upon, or derived from an established traditional foundation or practice.
-
D.
hasTraditionalFormIn
Indicates that something possesses a customary or historically established form or representation within a specified context, system, or location.
-
E.
hasTraditionalSymbol
Indicates that something is associated with or represented by a conventional or culturally established symbol.
- 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_69e0b4a3320881909495ae8bc30bc2dc |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67838744481909069b76b25dd4bb9 |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:24 a.m.