Triple
T18529110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laravel Sanctum |
E452789
|
entity |
| Predicate | storesTokensIn |
P63988
|
FINISHED |
| Object | personal_access_tokens table |
—
|
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: personal_access_tokens table | Statement: [Laravel Sanctum, storesTokensIn, personal_access_tokens table]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storesTokensIn Context triple: [Laravel Sanctum, storesTokensIn, personal_access_tokens table]
-
A.
storesInterfaceIn
Indicates that one entity keeps or maintains an interface definition within another entity (such as a container, module, or storage location).
-
B.
storesKeys
Indicates that one entity holds or retains the keys belonging to or used by another entity.
-
C.
storesIndexesIn
Indicates that one entity maintains and holds index data within another storage entity or system.
-
D.
storeType
Indicates the category or kind of store associated with an entity, such as its retail or service type.
-
E.
store
chosen
Indicates that one entity keeps or holds another entity in a place or system for future use or access.
- 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e533fad2d081908395914d6a6b4eb1 |
completed | April 19, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:37 a.m.