Triple
T28683291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea Scouts (Boy Scouts of America) |
E726062
|
entity |
| Predicate | skillArea |
P18508
|
FINISHED |
| Object | seamanship |
—
|
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: seamanship | Statement: [Sea Scouts (Boy Scouts of America), skillArea, seamanship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: skillArea Context triple: [Sea Scouts (Boy Scouts of America), skillArea, seamanship]
-
A.
skillSet
Indicates that an entity possesses or is associated with a particular collection of skills or competencies.
-
B.
competenceArea
chosen
Indicates that one entity has a particular domain, field, or area in which it possesses competence, expertise, or responsibility.
-
C.
skillType
Indicates the specific category or kind of skill that characterizes or classifies an associated skill-related entity or action.
-
D.
skillAssessed
Indicates that an entity’s skill or competency has been evaluated or measured, typically by another agent or process.
-
E.
skilledIn
Indicates that an entity possesses ability, expertise, or proficiency in performing or using another entity (such as a task, tool, or domain).
- 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_69f01d867608819086bc3e6b4f9de866 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6567e99848190a67a9b7071bad339 |
completed | May 2, 2026, 7:54 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 5:10 a.m.