Triple
T33719917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tenderfoot rank |
E863980
|
entity |
| Predicate | requiresScoutmasterConference |
P67164
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tenderfoot rank, requiresScoutmasterConference, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresScoutmasterConference Context triple: [Tenderfoot rank, requiresScoutmasterConference, yes]
-
A.
participantRequirement
chosen
Indicates that a certain condition, qualification, or constraint must be met by an entity in order to participate in a specified activity, event, or relationship.
-
B.
hasConferenceOrDivision
Indicates that an entity is associated with a specific conference or division within a larger organizational or competitive structure.
-
C.
hasConference
Indicates that an entity organizes, hosts, or is associated with a specific conference.
-
D.
badgeRequirement
Indicates that one entity specifies the conditions or criteria that must be met to obtain or qualify for a particular badge associated with another entity.
-
E.
requiresParticipationOf
Indicates that one entity’s occurrence, validity, or completion depends on the active involvement or participation of another entity.
- 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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff4fc6077c8190b8fd9b43fcfde986 |
completed | May 9, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69ff4e61fb648190a72f7918961ece9c |
completed | May 9, 2026, 3:10 p.m. |
Created at: May 1, 2026, 1:44 a.m.