Triple
T18204815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falcon |
E435875
|
entity |
| Predicate | notableUserBase |
P7127
|
FINISHED |
| Object | open-source AI community |
—
|
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: open-source AI community | Statement: [Falcon, notableUserBase, open-source AI community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableUserBase Context triple: [Falcon, notableUserBase, open-source AI community]
-
A.
notableUser
Indicates that the user holds a special or distinguished status, such as being recognized, influential, or otherwise noteworthy within a given context.
-
B.
notableUserInterface
Indicates that an entity has a user interface that is particularly significant, prominent, or noteworthy in some context.
-
C.
notableBase
chosen
Indicates that a particular location serves as a significant or distinguished base or headquarters for an entity.
-
D.
notableUserAlias
Indicates that a user is known or recognized by a particular alternate name or alias.
-
E.
notableUserCommunity
Indicates that a user has a significant or distinguished presence, role, or recognition within a particular community.
- 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e222831081908f7d5500424e3acb |
completed | April 19, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4332155d88190b106d0dceb4554af |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:32 a.m.