Triple
T24101608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas Archeological Stewardship Network |
E597088
|
entity |
| Predicate | volunteerBased |
P138783
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Texas Archeological Stewardship Network, volunteerBased, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: volunteerBased Context triple: [Texas Archeological Stewardship Network, volunteerBased, true]
-
A.
usesVolunteers
chosen
Indicates that an entity relies on or engages volunteers to perform its activities or services.
-
B.
volunteeredFor
Indicates that an entity willingly offered their time or services to support or participate in an activity, cause, or organization.
-
C.
hasVolunteerBase
Indicates that an entity maintains or relies on a group of volunteers as a foundational support resource.
-
D.
volunteerLabel
Indicates that an entity is identified or tagged as a volunteer in relation to another entity or context.
-
E.
hasVolunteerBaseIn
Indicates that an organization maintains a core group of volunteers located in a specified place or region.
- 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_69e288c548048190a5c1018da1166a21 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dd29fe708190a94195ea607bd69e |
completed | April 29, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11 p.m.