Triple
T28683298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea Scouts (Boy Scouts of America) |
E726062
|
entity |
| Predicate | programMethod |
P859
|
FINISHED |
| Object | experiential learning |
—
|
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: experiential learning | Statement: [Sea Scouts (Boy Scouts of America), programMethod, experiential learning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programMethod Context triple: [Sea Scouts (Boy Scouts of America), programMethod, experiential learning]
-
A.
programmingMethod
Indicates the method, technique, or approach used to carry out a programming-related activity or task.
-
B.
programEntryMethod
Indicates that a method serves as the starting point or main entry method for executing a program or component.
-
C.
method
chosen
Indicates the technique, procedure, or process used by an entity to perform an action or achieve a result.
-
D.
program
Indicates that an entity creates, writes, or develops a computer program or software application.
-
E.
plannedMethod
Indicates that a particular method or procedure has been selected or designated in advance as the intended way to carry out an action or achieve a goal.
- 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_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 28, 2026, 5:10 a.m.