Triple
T7600995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Complex Systems Summer School |
E179981
|
entity |
| Predicate | usesMethodsFrom |
P33646
|
FINISHED |
| Object | physics |
—
|
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: physics | Statement: [Complex Systems Summer School, usesMethodsFrom, physics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMethodsFrom Context triple: [Complex Systems Summer School, usesMethodsFrom, physics]
-
A.
usesMethods
chosen
Indicates that one entity employs, applies, or relies on specific methods or techniques to perform an action or achieve a result.
-
B.
providesMethodsFor
Indicates that one entity supplies or defines methods or functionalities that can be used or invoked by another entity.
-
C.
usesClass
Indicates that one entity makes use of, depends on, or is implemented using a particular class in its structure or behavior.
-
D.
implementedFrom
Indicates that one entity is realized, built, or executed based on the design, specification, or definition provided by another entity.
-
E.
usesImplement
Indicates that one entity employs or makes use of another entity as a tool, instrument, or means to perform an action or achieve a purpose.
- 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_69c69f3567008190ab01d2ca7b53584a |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9d9c55c8190841f3bf3225c096a |
completed | March 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e2e42c8190afc802c4796c9cc2 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:53 p.m.