Triple
T33731043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noah Ringer |
E864275
|
entity |
| Predicate | basedOnSkill |
P96902
|
FINISHED |
| Object | martial arts |
—
|
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: martial arts | Statement: [Noah Ringer, basedOnSkill, martial arts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnSkill Context triple: [Noah Ringer, basedOnSkill, martial arts]
-
A.
basedOnAbilityOf
Indicates that something is determined, derived, or decided according to the abilities or capabilities of a particular entity.
-
B.
indicatesSkill
chosen
Indicates a relationship where one entity possesses, demonstrates, or is associated with a particular skill represented by another entity.
-
C.
basedOnExperience
Indicates that something is determined, chosen, or formed according to prior experience or experiential knowledge.
-
D.
skilledIn
Indicates that an entity possesses ability, expertise, or proficiency in performing or using another entity (such as a task, tool, or domain).
-
E.
basedOnExpertiseOf
Indicates that something is determined, derived, or justified using the knowledge, skills, or judgment of a particular expert or group of experts.
- 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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69feced53a7c819098ec474fb7d514b0 |
completed | May 9, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69fecd9cd5288190aac8b4e04a7ee78e |
completed | May 9, 2026, 6:01 a.m. |
Created at: May 1, 2026, 1:44 a.m.